CVE-2015-5306
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 · uneditedOpenStack Ironic Inspector (aka ironic-inspector or ironic-discoverd), when debug mode is enabled, might allow remote attackers to access the Flask console and execute arbitrary Python code by triggering an error.
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 confidenceWhen OpenStack Ironic Inspector runs with debug mode enabled, an error condition exposes the Flask/Werkzeug debugger to remote attackers, allowing arbitrary Python code execution via the debugger's interactive console.
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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 Ironic Inspector is installedCheck for the ironic-inspector service process or package: systemctl status ironic-inspector, or rpm -qa | grep ironic-inspector, or pip list | grep ironic-inspectorAffected if Ironic Inspector package or service is found on the system
-
Locate the Ironic Inspector configuration fileCommon paths: /etc/ironic-inspector/inspector.conf, /etc/ironic-inspector.conf, or check the service init script for CONF_FILE parameterAffected if Configuration file exists and is readable
-
Check if debug mode is enabled in the configSearch for 'debug' setting in the configuration file: grep -i '^debug' /etc/ironic-inspector/inspector.conf or similar path. Look for debug=true, debug = True, or DEBUG=TrueAffected if debug is set to True, yes, or 1 in the configuration file
-
Check for debug mode via environment variableInspect the service environment or startup script: env | grep -i debug, or cat /etc/sysconfig/ironic-inspector, or ps aux | grep inspector to see startup parametersAffected if DEBUG environment variable is set to true or 1
-
Verify network exposure of the serviceCheck if the inspector service listens on a non-localhost interface: netstat -tlnp | grep 5050 or ss -tlnp | grep 5050 (default port), and verify firewall rules allow remote accessAffected if Service listens on 0.0.0.0 or an external IP and is accessible from remote networks
A system is affected if OpenStack Ironic Inspector is installed AND debug mode is enabled (debug=True/yes in config or environment) AND the service is network-accessible to remote attackers.
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 dataDisable debug mode in production by setting debug=False in the Ironic Inspector configuration; ensure debug mode is never enabled in publicly-accessible deployments.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5306 — 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-2015-5306 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