# CVE-2024-43812: Kieback&Peter DDC4000 Series Path Traversal Insufficiently Protected Credentials

> An unauthenticated attacker can read system password hashes from /etc/passwd on Kieback&Peter DDC4000 series controllers.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2024
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-qvxh-rxm2-vq3p

## What is CVE-2024-43812?

CVE-2024-43812 is a high-severity vulnerability in Kieback&Peter DDC4002, published on 22 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kieback & Peter's DDC4000 series has an insufficiently protected credentials vulnerability, which may allow an unauthenticated attacker with access to /etc/passwd to read the password hashes of all users on the system.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2024-43812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-43812 is a high-severity vulnerability in Kieback&Peter DDC4002, published on 22 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-43812 in the wild and no public exploit code.

Affected product: Kieback&Peter DDC4002. 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-43812/ (Markdown: https://insights.sbomify.com/CVE-2024-43812/index.md)
```

## Sources

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

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