dbcve.org
IgnitionApplication · Inductiveautomation

CVE-2015-0995

MEDIUM · 5.0 CVSS v2.0 Published 2015-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Inductive Automation Ignition 7.7.2 uses MD5 password hashes, which makes it easier for context-dependent attackers to obtain access via a brute-force attack.

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

Inductive Automation Ignition version 7.7.2 stores user passwords using MD5 hash algorithm, which is cryptographically weak and susceptible to fast brute-force attacks. An attacker with access to the password hashes can easily crack them due to MD5's known vulnerabilities and speed.

MitigationUpgrade Ignition to a version that uses modern password hashing algorithms such as bcrypt, scrypt, or PBKDF2 with appropriate work factors. Also enforce strong password policies and implement account lockout mechanisms.

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
IgnitionApplication
Affected:= 7.7.2

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

AV:N/AC:L/Au:N/C:P/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 the installed Ignition version
    Check the Ignition installation by reviewing startup logs, version.info file, or the gateway configuration web interface for the exact version number
    Affected if The installed version is exactly 7.7.2
  2. Locate the user database or password storage
    Find the user database file or configuration where user credentials are stored - typically in the Ignition data directory or database connection settings
    Affected if The user database or configuration file is accessible and contains password hashes
  3. Examine the password hash format
    Inspect the stored password hashes in the user database or config file to determine the hashing algorithm used
    Affected if The password hashes appear as 32-character hexadecimal strings typical of MD5, indicating weak hashing is in use

You are affected only if your installed Ignition version is exactly 7.7.2 AND your user password storage uses MD5 hashing rather than a modern algorithm like bcrypt, scrypt, or PBKDF2

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Ignition to a version that uses modern password hashing algorithms such as bcrypt, scrypt, or PBKDF2 with appropriate work factors. Also enforce strong password policies and implement account lockout mechanisms.

Fix this in Ignition Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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