CVE-2015-7907
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 · uneditedDirectory traversal vulnerability in the web server on Honeywell Midas gas detectors before 1.13b3 and Midas Black gas detectors before 2.13b3 allows remote attackers to bypass authentication, and write to a configuration file or trigger a calibration or test, via unspecified vectors.
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 confidenceDirectory traversal vulnerability in the embedded web server of Honeywell Midas and Mida Black gas detectors allows remote unauthenticated attackers to bypass authentication via path traversal sequences (e.g., '../'), enabling writes to configuration files and triggering of calibration/test functions.
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<= 2.13b1<= 1.13b1CVSS 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
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
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 Midas devices on the networkScan network for Honeywell Midas or Midas Black gas detectors, typically accessible via HTTP on port 80 or custom ports. Check device inventory or perform network discovery to locate these specific devices.Affected if Honeywell Midas or Midas Black gas detectors are present on the network.
-
Determine the installed firmware versionAccess the device web interface and navigate to the About or System Information page, or use the device's management interface to retrieve the firmware version string.Affected if The firmware version is 1.13b1 or earlier for Midas, or 2.13b1 or earlier for Midas Black.
-
Verify the embedded web server is accessibleAttempt HTTP or HTTPS connection to the device IP address on the web server port (commonly port 80). Confirm the web interface responds to requests.Affected if The device web interface is reachable over the network.
-
Check if authentication can be bypassed via path traversalSend a crafted HTTP request with path traversal sequences (such as ../) to the web server endpoint, for example: GET /../../../../etc/passwd or similar paths used for configuration file access. Compare the response to normal authenticated requests.Affected if Path traversal sequences return configuration files or bypass authentication without valid credentials.
A defender is affected if their network contains Honeywell Midas or Midas Black gas detectors running firmware versions 1.13b1 or earlier (Midas) or 2.13b1 or earlier (Midas Black), with the embedded web server accessible and vulnerable to path traversal bypass.
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 dataUpdate Midas firmware to 1.13b3 or later, and Midas Black to 2.13b3 or later. If patching is not immediately feasible, restrict network access to the device web interface via firewall or VLAN segmentation.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7907 — 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-7907 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