# CVE-2005-4532: Privilege escalation in n/a

> Local attackers can escalate privileges to root by exploiting LD_PRELOAD in scponlyc when chroot directories are used.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** Yes
- **Published:** 28 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-24xx-ff7h-g5rx

## What is CVE-2005-4532?

CVE-2005-4532 is a high-severity vulnerability in n/a, published on 28 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

scponlyc in scponly 4.1 and earlier, when the operating system supports LD_PRELOAD mechanisms, allows local users to execute arbitrary code with root privileges by creating a chroot directory in their home directory, hard linking to a system setuid application, and using a modified LD_PRELOAD to modify expected function calls in the setuid application.

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

It affects 1 product.


Products: Scponly Scponly.

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

Apply the vendor's patch.

## Is CVE-2005-4532 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6350](https://insights.sbomify.com/CVE-2007-6350/): Security feature bypass in n/a (high 8.5)
- [CVE-2005-4533](https://insights.sbomify.com/CVE-2005-4533/): Command injection in n/a (high 7.5)
- [CVE-2002-1469](https://insights.sbomify.com/CVE-2002-1469/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4532 is a high-severity vulnerability in n/a, published on 28 Dec 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-4532 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-4532/ (Markdown: https://insights.sbomify.com/CVE-2005-4532/index.md)
```

## Sources

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

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