# CVE-2005-0627: Path traversal in n/a

> Local attackers can execute arbitrary code by placing malicious libraries in a world-writable build directory, bypassing standard library path settings.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 4 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-96vr-52vh-8q5x

## What is CVE-2005-0627?

CVE-2005-0627 is a medium-severity path traversal vulnerability in n/a, published on 4 Mar 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Qt before 3.3.4 searches the BUILD_PREFIX directory, which could be world-writable, to load shared libraries regardless of the LD_LIBRARY_PATH environment variable, which allows local users to execute arbitrary programs.

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

It affects 1 product.


Products: Trolltech Qt.

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

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

## Is CVE-2005-0627 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4137](https://insights.sbomify.com/CVE-2007-4137/): Memory corruption in n/a (high 7.5)
- [CVE-2004-0691](https://insights.sbomify.com/CVE-2004-0691/): Memory corruption in n/a (high 7.5)
- [CVE-2007-3388](https://insights.sbomify.com/CVE-2007-3388/): Code injection in n/a (medium 6.8)
- [CVE-2004-0692](https://insights.sbomify.com/CVE-2004-0692/): Null dereference in n/a (medium 5.0)
- [CVE-2004-0693](https://insights.sbomify.com/CVE-2004-0693/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0627 is a medium-severity path traversal vulnerability in n/a, published on 4 Mar 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-0627 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-0627/ (Markdown: https://insights.sbomify.com/CVE-2005-0627/index.md)
```

## Sources

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

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