# CVE-2024-9929: Information disclosure in NSD570 Teleprotection Equipment

> Authenticated users can access device logs containing sensitive login information and timestamps on Hitachi Energy NSD570 equipment.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 26 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-cq6j-fwr2-x2rr

## What is CVE-2024-9929?

CVE-2024-9929 is a medium-severity vulnerability in Hitachi Energy NSD570 Teleprotection Equipment, published on 26 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability exists in NSD570 that allows any authenticated
user to access all device logs disclosing login information with
timestamps.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2024-9929 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9929 is a medium-severity vulnerability in Hitachi Energy NSD570 Teleprotection Equipment, published on 26 Nov 2024. 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-9929 in the wild and no public exploit code.

Affected product: Hitachi Energy NSD570 Teleprotection Equipment. 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-9929/ (Markdown: https://insights.sbomify.com/CVE-2024-9929/index.md)
```

## Sources

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

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