OpenstackApplication · Redhat
CVE-2019-3895
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 · uneditedAn access-control flaw was found in the Octavia service when the cloud platform was deployed using Red Hat OpenStack Platform Director. An attacker could cause new amphorae to run based on any arbitrary image. This meant that a remote attacker could upload a new amphorae image and, if requested to spawn new amphorae, Octavia would then pick up the compromised image.
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 · high confidenceA missing access control in Octavia (load balancer service) allows remote attackers to specify arbitrary images for amphorae (load balancer VMs) when deployed via Red Hat OpenStack Platform Director. Without proper authorization checks, Octavia will use any uploaded image when provisioning new amphorae, enabling remote code execution through a compromised amphorae image.
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 data
OpenstackApplication
= 12< 0.9.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/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.
-
Confirm Octavia is deployedRun 'openstack service list' or check if the octavia service is registered and active in the OpenStack environmentAffected if Octavia load balancer service is not present in the environment
-
Check Octavia versionRun 'octavia version' or query the Octavia API endpoint for its version informationAffected if Octavia version is less than 0.9.0
-
Check Red Hat OpenStack Platform versionRun 'openstack version' or check the RHOSP version via subscription-manager or the undercloud inventoryAffected if Red Hat OpenStack Platform version equals 12
-
Verify authorization controls on amphora image selectionExamine Octavia configuration files (octavia.conf) for 'image_driver' settings and review the policy.json for rules controlling image upload and selection permissions. Check if any non-admin user can specify a custom image when creating a load balancer amphora.Affected if No authorization policy exists or is enforced to restrict which images can be used for amphorae, allowing arbitrary image specification
-
Check for image whitelist or signature verificationReview Octavia configuration for image validation settings. Look for any configured whitelist or signature verification mechanism in the amphora image handling configuration.Affected if No image whitelist or signature verification is configured for amphorae images
The environment is affected if Octavia version is less than 0.9.0 (or RHOSP 12 is used) AND no proper authorization controls exist to restrict which images can be used for amphorae provisioning.
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 data0.9.0
Restrict image upload/selection permissions to only trusted administrators and implement image whitelisting or signature verification to ensure only approved amphorae images can be used by Octavia.
Fix this in Openstack
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3895 — 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-2019-3895 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