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

CVE-2025-5517

MEDIUM · 6.8 CVSS v3.1 Published 2025-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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 (UL40/80A), ABB Terra AC wallbox (UL32A), ABB Terra AC wallbox (MID/ CE) -Terra AC MID, ABB Terra AC wallbox (MID/ CE) -Terra AC Juno CE, ABB Terra AC wallbox (MID/ CE) -Terra AC PTB, ABB Terra AC wallbox (JP).This issue affects Terra AC wallbox (UL40/80A): through 1.8.32; Terra AC wallbox (UL32A): through 1.8.2; Terra AC wallbox (MID/ CE) -Terra AC MID: through 1.8.32; Terra AC wallbox (MID/ CE) -Terra AC Juno CE: through 1.8.32; Terra AC wallbox (MID/ CE) -Terra AC PTB: through 1.8.21; Terra AC wallbox (JP): through 1.8.2.

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 charging stations allows memory corruption on the heap, potentially enabling authenticated attackers to execute arbitrary code or cause denial of service. The vulnerability affects multiple Terra AC wallbox variants across UL, MID/CE, and JP regions with firmware versions up to the specified thresholds.

MitigationUpdate firmware to versions newer than the affected thresholds (1.8.32 for UL40/80A/MID/Juno CE, 1.8.21 for PTB, 1.8.2 for UL32A/JP). If patches are unavailable, implement network segmentation and restrict access to authenticated personnel only.

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

CVSS:3.1/AV:N/AC:H/PR:L/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 device model
    Locate the device nameplate or check the charging station's web interface/system info to confirm it is an ABB Terra AC wallbox variant (UL40, UL80A, UL32A, MID, CE, PTB, Juno CE, or JP models).
    Affected if The device is not an ABB Terra AC wallbox charging station.
  2. Check the installed firmware version
    Access the Terra AC wallbox web interface (typically via IP address on the local network) and navigate to Settings > Device Info or System > Firmware to view the current firmware version. Alternatively, check via the ABB charging management platform if available.
    Affected if The firmware version is 1.8.32 or lower for UL40/80A/MID/Juno CE models, 1.8.21 or lower for PTB models, or 1.8.2 or lower for UL32A/JP models.
  3. Determine if remote/network management is enabled
    Check the device network settings via the web interface or management platform to see if Ethernet, Wi-Fi, or cellular network connectivity is enabled, which would expose the device to remote attackers.
    Affected if Network connectivity is enabled and the device is accessible from untrusted networks.
  4. Verify authentication configuration
    Check the user authentication settings in the Terra AC administration panel to determine if default credentials are in use or if weak authentication is configured.
    Affected if Default credentials remain unchanged or authentication is disabled.

A user is affected if their Terra AC wallbox runs firmware at or below the version thresholds (1.8.32/1.8.21/1.8.2 depending on model) and has network access that could allow authenticated attackers to exploit the heap overflow.

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

Update firmware to versions newer than the affected thresholds (1.8.32 for UL40/80A/MID/Juno CE, 1.8.21 for PTB, 1.8.2 for UL32A/JP). If patches are unavailable, implement network segmentation and restrict access to authenticated personnel only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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