dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-10504

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
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
Heap-based Buffer Overflow vulnerability in ABB Terra AC wallbox.This issue affects Terra AC wallbox: through 1.8.33.

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 · moderate confidence

Heap-based buffer overflow vulnerability in ABB Terra AC wallbox electric vehicle charging stations, affecting all versions through 1.8.33. The overflow occurs in heap memory, potentially allowing an attacker to corrupt memory and potentially execute arbitrary code or cause denial of service.

MitigationContact ABB for the latest firmware patch and apply appropriate vendor-provided updates. Until patched, minimize network exposure of the wallbox and monitor for unauthorized access attempts.

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:H/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. Identify the installed firmware version
    Access the ABB Terra AC wallbox web interface or administrative panel and navigate to the firmware/version information section. Alternatively, check via the device's management API or display if available.
    Affected if The displayed firmware version is 1.8.33 or any earlier version (e.g., 1.8.32, 1.7.x, etc.)
  2. Compare version against affected range
    Verify if the installed firmware version number is less than or equal to 1.8.33. All versions at or below this number are within the affected range.
    Affected if The installed version is 1.8.33 or any version prior to it
  3. Confirm network accessibility of the wallbox
    Determine if the wallbox administrative interface or charging management network service is accessible from untrusted networks (such as the public internet or guest networks). Check firewall rules, port exposures, and VLAN configurations.
    Affected if The device administrative interface is directly exposed to untrusted networks without firewall protection

You are affected if your ABB Terra AC wallbox runs firmware version 1.8.33 or earlier and is network-accessible to potential attackers.

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

Contact ABB for the latest firmware patch and apply appropriate vendor-provided updates. Until patched, minimize network exposure of the wallbox and monitor for unauthorized access attempts.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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