# CVE-2024-13930: Authenticated Unchecked Loop Condition

> Authenticated attackers can cause denial of service by exploiting an unchecked loop condition in ABB ASPECT Enterprise systems.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/S:N/AU:N/R:U/V:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-5fcg-gph2-wcvg

## What is CVE-2024-13930?

CVE-2024-13930 is a medium-severity denial of service vulnerability in ABB ASPECT-Enterprise, published on 22 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An Unchecked Loop Condition in ASPECT provides an attacker the ability to maliciously consume system resources if session administrator credentials become compromised
This issue affects ASPECT-Enterprise: through 3.08.03; NEXUS Series: through 3.08.03; MATRIX Series: through 3.08.03.

Weakness: CWE-606 (Unchecked Input for Loop Condition)

## Which versions are affected by CVE-2024-13930?


## How do I fix CVE-2024-13930?

No fix has been published for CVE-2024-13930 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-13930 being exploited?

There is no known exploitation of CVE-2024-13930 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13930 and fix it if it is affected.

What it is: CVE-2024-13930 is a medium-severity denial of service vulnerability in ABB ASPECT-Enterprise, published on 22 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13930 in the wild and no public exploit code.

Affected product: ABB ASPECT-Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13930/ (Markdown: https://insights.sbomify.com/CVE-2024-13930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13930
- OSV: https://osv.dev/vulnerability/CVE-2024-13930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13930/
Summaries are generated and may contain mistakes; the official description above is the record.