dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-6072

HIGH · 7.5 CVSS v3.1 Published 2025-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Stack-based Buffer Overflow vulnerability in ABB RMC-100, ABB RMC-100 LITE. When the REST interface is enabled by the user, and an attacker gains access to the control network, and CVE-2025-6074 is exploited, the attacker can use the JSON configuration to overflow the date of expiration field.This issue affects RMC-100: from 2105457-043 through 2105457-045; RMC-100 LITE: from 2106229-015 through 2106229-016.

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

A stack-based buffer overflow vulnerability in ABB RMC-100 and RMC-100 LITE allows overflow of the date of expiration field in JSON configuration. Exploitation requires the REST interface to be enabled, network access to the control network, and prior exploitation of CVE-2025-6074.

MitigationDisable the REST interface if not required, implement network segmentation to restrict control network access, and apply vendor firmware updates to address affected versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Integrity
None
Availability
High

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

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. Confirm device model
    Check the device web interface, system information page, or network service banners for ABB RMC-100 or RMC-100 LITE identification
    Affected if Device is not ABB RMC-100 or RMC-100 LITE - not affected
  2. Verify REST interface is enabled
    Access the device administration or configuration panel and check whether the REST/REST API interface setting is enabled
    Affected if REST interface is disabled - not affected since this is a required condition for exploitation
  3. Assess REST interface network exposure
    Determine if the REST service ports are accessible from the control network or external network segments by reviewing network ACLs, firewall rules, or attempting connectivity to typical HTTP/HTTPS ports
    Affected if REST interface is only accessible from isolated management network - lower risk but still requires checking

Device is likely affected if it is an ABB RMC-100 or RMC-100 LITE with REST interface enabled and accessible from the control network, especially if CVE-2025-6074 is also present as a prerequisite for exploitation

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

Disable the REST interface if not required, implement network segmentation to restrict control network access, and apply vendor firmware updates to address affected versions.

Recommended fix Moderate confidence

Firmware versions beyond 2105457-045 for RMC-100 and beyond 2106229-016 for RMC-100 LITE (obtain exact version from ABB security advisory)

  1. 1. Identify the current firmware version of the ABB RMC-100 or RMC-100 LITE device by accessing the device management interface.
  2. 2. Navigate to ABB's official support portal at search.abb.com to obtain the latest firmware version.
  3. 3. Review ABB's security advisory for CVE-2025-6072 to confirm the fixed firmware version for your specific device model.
  4. 4. Before upgrading, ensure the device is backed up according to ABB's documentation procedures.
  5. 5. Upgrade the firmware to the version that addresses CVE-2025-6072 (versions after 2105457-045 for RMC-100 and after 2106229-016 for RMC-100 LITE).
  6. 6. After upgrading, verify that the REST interface is properly secured if it must remain enabled.
  7. 7. Confirm the vulnerability is resolved by checking the firmware version and reviewing the security advisory.
Caveat Firmware upgrades on industrial control devices may require reconfiguration; verify all settings and ensure compatibility with connected systems before deploying to production

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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