# CVE-2024-51553: Predictable Filename

> Predictable filenames in ABB ASPECT products may expose sensitive information to attackers if administrator credentials are compromised.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-cgq3-4xq4-v94r

## What is CVE-2024-51553?

CVE-2024-51553 is a high-severity vulnerability in ABB ASPECT-Enterprise, published on 22 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Predictable filename vulnerabilities in ASPECT may expose sensitive information to a potential attacker if administrator credentials become compromisedThis issue affects ASPECT-Enterprise: through 3.*; NEXUS Series: through 3.*; MATRIX Series: through 3.*.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2024-51553 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51553 is a high-severity vulnerability in ABB ASPECT-Enterprise, published on 22 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51553 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-51553/ (Markdown: https://insights.sbomify.com/CVE-2024-51553/index.md)
```

## Sources

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

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