dbcve.org
OpenstackApplication · Redhat

CVE-2016-4985

HIGH · 7.5 CVSS v3.0 Published 2016-07-12
Fix available
A fix is available. Upgrade to after 4.2.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The ironic-api service in OpenStack Ironic before 4.2.5 (Liberty) and 5.x before 5.1.2 (Mitaka) allows remote attackers to obtain sensitive information about a registered node by leveraging knowledge of the MAC address of a network card belonging to that node and sending a crafted POST request to the v1/drivers/$DRIVER_NAME/vendor_passthru resource.

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 confidence

The ironic-api service in OpenStack Ironic contains an information disclosure vulnerability where a crafted POST request to the vendor_passthru endpoint allows remote attackers to obtain sensitive node information using only the MAC address of a network card, without proper authorization verification.

MitigationUpgrade Ironic to version 4.2.5+ (Liberty) or 5.1.2+ (Mitaka) to receive the patch that adds proper authorization checks before disclosing node information through the vendor_passthru API endpoint.

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
Affected:= 7.0= 8
Openstack IronicApplication
Affected:<= 4.2.4= 5.1.0= 5.1.1

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if OpenStack Ironic is deployed
    Check for the ironic-api service process or package: on RHEL/CentOS systems, run 'rpm -qa | grep ironic' or check for the ironic-api process with 'ps aux | grep ironic-api'. On Ubuntu/Debian, use 'dpkg -l | grep ironic' or check running processes.
    Affected if The ironic-api service is not installed or is not running.
  2. Determine the installed Ironic version
    Run the version check command for your package manager: 'rpm -qi openstack-ironic-common' (RHEL) or 'dpkg -s ironic-api' (Ubuntu). Alternatively, query the Ironic API version endpoint if accessible.
    Affected if The version cannot be determined or is not one of the known affected versions.
  3. Verify the version against affected ranges
    Compare your installed version number to the affected ranges: Red Hat OpenStack 7.0 or 8; Canonical Ironic versions 4.2.4 or lower, 5.1.0, or 5.1.1. If you are on Liberty (4.x) series, versions at or below 4.2.4 are affected. If on Mitaka (5.x), versions 5.1.0 and 5.1.1 are affected.
    Affected if Your installed version matches any of the affected versions listed.
  4. Check vendor_passthru endpoint accessibility
    Determine if the vendor_passthru API endpoint is exposed. Review your Ironic configuration file (typically /etc/ironic/ironic.conf) for the 'enabled_passthru' or 'vendor_passthru' setting, and check network exposure via API service configuration.
    Affected if The vendor_passthru endpoint is enabled and accessible from the network.
  5. Confirm the vulnerability condition
    The environment is vulnerable if: (1) Ironic version is one of the affected versions listed above, AND (2) the vendor_passthru endpoint is enabled. Both conditions must be true for exploitation.
    Affected if Both conditions are true: affected version running with vendor_passthru accessible.

You are affected if the ironic-api service is running a version matching Red Hat OpenStack 7.0, 8, or Canonical Ironic <= 4.2.4, 5.1.0, or 5.1.1, with the vendor_passthru endpoint enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.2.4
Interim mitigation

Upgrade Ironic to version 4.2.5+ (Liberty) or 5.1.2+ (Mitaka) to receive the patch that adds proper authorization checks before disclosing node information through the vendor_passthru API endpoint.

Fix this in Openstack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-4985 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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