# CVE-2005-2136: Misconfiguration in n/a

> Local attackers can read hashed passwords or execute arbitrary code due to insecure file permissions on Raritan Dominion SX console servers.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5hmj-phhp-xxgh

## What is CVE-2005-2136?

CVE-2005-2136 is a medium-severity vulnerability in n/a, published on 5 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Raritan Dominion SX (DSX) Console Servers DSX16, DSX32, DSX4, DSX8, and DSXA-48 set (1) world-readable permissions for /etc/shadow and (2) world-writable permissions for /bin/busybox, which allows local users to obtain hashed passwords or execute arbitrary code as other users.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2005-2136?

It affects 5 products.


Products: Raritan Dominion Sx16 Firmware, Raritan Dominion Sx32 Firmware, Raritan Dominion Sx4 Firmware, Raritan Dominion Sx8 Firmware, Raritan Dominion Sxa-48 Firmware.

## How do I fix CVE-2005-2136?

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

## Is CVE-2005-2136 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2136 and fix it if it is affected.

What it is: CVE-2005-2136 is a medium-severity vulnerability in n/a, published on 5 Jul 2005. 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-2005-2136 in the wild and no public exploit code.

Affected product: n/a. 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-2005-2136/ (Markdown: https://insights.sbomify.com/CVE-2005-2136/index.md)
```

## Sources

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

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