CVE-2016-4383
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe glance-manage db in all versions of HPE Helion Openstack Glance allows deleted image ids to be reassigned, which allows remote authenticated users to cause other users to boot into a modified image without notification of the change.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn HPE Helion OpenStack Glance, the glance-manage db functionality allows deleted image IDs to be reassigned to new images. An authenticated remote attacker can exploit this by deleting an image and then creating a new image with the same ID, causing other users who provision instances to boot into the attacker's modified image without any notification of the ID reuse.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify HPE Helion OpenStack Glance deploymentRun 'glance --version' or check the installed Glance package version via the package manager (e.g., 'rpm -qa | grep glance' or 'dpkg -l | grep glance')Affected if The package name or banner indicates HPE Helion OpenStack Glance is installed
-
Verify the Glance API service is runningRun 'glance image-list' as the cloud admin to retrieve all image metadata, or query the Glance API endpoint directlyAffected if The Glance service responds and lists images in the environment
-
Inspect image ID history for reuse patternsQuery the Glance database (typically in MySQL/PostgreSQL as the 'glance' user) with: SELECT image_id, created_at, deleted_at FROM image_members WHERE deleted_at IS NOT NULL GROUP BY image_id HAVING COUNT(*) > 1; or check the image table for duplicate image_id values across different created_at timestampsAffected if The database returns any image IDs that appear multiple times with different creation timestamps, indicating ID reuse has occurred
-
Check for deleted images that may have been recreatedCompare the current image list ('glance image-list') against any existing audit logs or image history records to identify if any current image IDs match previously deleted image IDsAffected if Any current active image has an ID that matches a previously deleted image from the audit history
A defender is affected if HPE Helion OpenStack Glance is deployed and the database shows any instances of image ID reuse, where deleted image IDs have been assigned to new images.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement unique ID generation that prevents reassignment of deleted image IDs, or implement user notification mechanisms when image IDs are reused.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-4383 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data