# CVE-2005-0134: Race condition in n/a

> Local attackers can hijack X server sockets due to insecure directory creation in /tmp, potentially leading to privilege escalation or data access.

- **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:** 18 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hr44-4p4m-vp56

## What is CVE-2005-0134?

CVE-2005-0134 is a medium-severity vulnerability in Sco Unixware, published on 18 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The X server in SCO UnixWare 7.1.1, 7.1.3, and 7.1.4 does not properly create socket directories in /tmp, which could allow attackers to hijack local sockets.

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

It affects 1 product.


Products: Sco Unixware.

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

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

## Is CVE-2005-0134 being exploited?

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

## Other vulnerabilities in Sco Unixware

- [CVE-2000-0348](https://insights.sbomify.com/CVE-2000-0348/): Privilege escalation in n/a (critical 10.0)
- [CVE-1999-0836](https://insights.sbomify.com/CVE-1999-0836/): Path traversal in n/a (critical 10.0)
- [CVE-2000-0003](https://insights.sbomify.com/CVE-2000-0003/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-0026](https://insights.sbomify.com/CVE-2000-0026/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1552](https://insights.sbomify.com/CVE-2009-1552/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0134 is a medium-severity vulnerability in Sco Unixware, published on 18 May 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-0134 in the wild and no public exploit code.

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

## Sources

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

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