# CVE-2024-38877: Hardcoded credentials in Omnivise T3000 Application Server R9.2

> Attackers with shell or physical access can retrieve unprotected initial system credentials, enabling lateral movement within the network.

- **Severity:** High 8.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2024
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-5f2h-gxrx-j654

## What is CVE-2024-38877?

CVE-2024-38877 is a high-severity vulnerability in Siemens Omnivise T3000 Application Server R9.2, published on 2 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in Omnivise T3000 Application Server R9.2 (All versions), Omnivise T3000 Domain Controller R9.2 (All versions), Omnivise T3000 Network Intrusion Detection System (NIDS) R9.2 (All versions), Omnivise T3000 Product Data Management (PDM) R9.2 (All versions), Omnivise T3000 R8.2 SP3 (All versions), Omnivise T3000 R8.2 SP4 (All versions), Omnivise T3000 Security Server R9.2 (All versions), Omnivise T3000 Terminal Server R9.2 (All versions), Omnivise T3000 Thin Client R9.2 (All versions), Omnivise T3000 Whitelisting Server R9.2 (All versions). The affected devices stores initial system credentials without sufficient protection.  An attacker with remote shell access or physical access could retrieve the credentials leading to confidentiality loss allowing the attacker to laterally move within the affected network.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 7 products.


Products: Siemens Omnivise T3000 Application Server, Siemens Omnivise T3000 Domain Controller, Siemens Omnivise T3000 Network Intrusion Detection System, Siemens Omnivise T3000 Product Data Management, Siemens Omnivise T3000 Terminal Server, Siemens Omnivise T3000 Thin Client, Siemens Omnivise T3000 Whitelisting Server.

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

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

## Is CVE-2024-38877 being exploited?

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

## Other vulnerabilities in Siemens Omnivise T3000 Application Server R9.2

- [CVE-2024-38879](https://insights.sbomify.com/CVE-2024-38879/): Auth bypass in Omnivise T3000 Application Server R9.2 (high 8.7)
- [CVE-2024-38876](https://insights.sbomify.com/CVE-2024-38876/): Privilege escalation in Omnivise T3000 Application Server R9.2 (high 8.5)
- [CVE-2024-38878](https://insights.sbomify.com/CVE-2024-38878/): Path traversal in Omnivise T3000 Application Server R9.2 (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38877 is a high-severity vulnerability in Siemens Omnivise T3000 Application Server R9.2, published on 2 Aug 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-38877 in the wild and no public exploit code.

Affected product: Siemens Omnivise T3000 Application Server R9.2. 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-38877/ (Markdown: https://insights.sbomify.com/CVE-2024-38877/index.md)
```

## Sources

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

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