yahoo-eng-team team mailing list archive

[Grant Murphy <grant.murphy@xxxxxx>]

Removed the OSSA task and opened the bug. Will leave it to the Nova PTL
to close.

** Changed in: ossa
       Status: Incomplete => Won't Fix

** Information type changed from Private Security to Public

** No longer affects: ossa

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1538061

Title:
  Ensure that LVM escapes instance names for device names correctly

Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  This issue is being treated as a potential security risk under
  embargo. Please do not make any public mention of embargoed (private)
  security vulnerabilities before their coordinated publication by the
  OpenStack Vulnerability Management Team in the form of an official
  OpenStack Security Advisory. This includes discussion of the bug or
  associated fixes in public forums such as mailing lists, code review
  systems and bug trackers. Please also avoid private disclosure to
  other individuals not already approved for access to this information,
  and provide this same reminder to those who are made aware of the
  issue prior to publication. All discussion should remain confined to
  this private bug report, and any proposed fixes should be added to the
  bug as attachments.

  --

  This came up at the nova mid-cycle. We know that LVM uses the instance
  name (which is user configurable) as the LVM device name for devices
  it creates. We should audit to ensure that's correctly escaped. We
  should also check where else we do something similar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538061/+subscriptions