dbcve.org
Midas FirmwareOperating system · Honeywell

CVE-2015-7908

HIGH · 9.3 CVSS v2.0 Published 2015-12-21
Fix available
A fix is available. Upgrade to after 2.13b1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Honeywell Midas gas detectors before 1.13b3 and Midas Black gas detectors before 2.13b3 allow remote attackers to discover cleartext passwords by sniffing the network.

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

Honeywell Midas and Midas Black gas detector firmware versions prior to 1.13b3 and 2.13b3 respectively transmit user credentials in cleartext over the network. An attacker with the ability to sniff network traffic can intercept these plaintext passwords and gain unauthorized access to the device.

MitigationUpgrade Midas firmware to version 1.13b3 or later and Midas Black firmware to 2.13b3 or later. Additionally, isolate these devices on a dedicated network segment and implement encryption (e.g., VPN) for any remote access to reduce the risk of credential interception.

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
Midas FirmwareOperating system
Affected:<= 1.13b1
Midas Black FirmwareOperating system
Affected:<= 2.13b1

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 the device model
    Locate the Honeywell gas detector on the network and confirm whether it is a Midas or Midas Black model. This information is typically displayed on the device web interface login page, in the device documentation, or on the physical device label.
    Affected if The device is a Honeywell Midas or Midas Black gas detector.
  2. Determine the installed firmware version
    Access the device web interface and navigate to the System Information, About, or Status page to view the firmware version. If the web interface is not accessible, consult the device documentation for alternative methods such as SNMP or serial console.
    Affected if The firmware version cannot be confirmed or is visible in the interface.
  3. Compare firmware version to affected ranges
    Compare the identified firmware version against the affected ranges: Midas firmware version 1.13b1 or earlier, or Midas Black firmware version 2.13b1 or earlier.
    Affected if The installed Midas firmware is 1.13b1 or lower, or the installed Midas Black firmware is 2.13b1 or lower.
  4. Verify the authentication protocol in use
    Attempt to log into the device web interface and observe whether the login page uses HTTP (unencrypted) or HTTPS (encrypted). Check the browser address bar for http:// versus https:// and look for a padlock icon indicating SSL/TLS encryption.
    Affected if The device web interface is accessible over plain HTTP without encryption.

You are affected if the device is a Honeywell Midas or Midas Black running firmware version 1.13b1 or lower (Midas) or 2.13b1 or lower (Midas Black), and user credentials are transmitted over an unencrypted network connection.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.13b1
Interim mitigation

Upgrade Midas firmware to version 1.13b3 or later and Midas Black firmware to 2.13b3 or later. Additionally, isolate these devices on a dedicated network segment and implement encryption (e.g., VPN) for any remote access to reduce the risk of credential interception.

Recommended fix High confidence

Midas Firmware 1.13b3 or Midas Black Firmware 2.13b3

  1. Download the fixed firmware version (Midas Firmware 1.13b3 or Midas Black Firmware 2.13b3) from the official Honeywell source
  2. Back up the current device configuration before proceeding with the update
  3. Access the Midas/Midas Black gas detector administrative interface
  4. Upload and apply the new firmware version to the device
  5. Verify the firmware upgrade was successful by checking the version number in the device
  6. Immediately change all passwords that may have been exposed, as attackers could have sniffed them from network traffic
  7. After upgrading, verify that passwords are no longer transmitted in cleartext on the network
Caveat Review release notes for any configuration changes required after firmware upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Midas Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7908 — 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-2015-7908 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