# CVE-2008-0893: Missing authorization in n/a

> Remote attackers can perform administrative actions due to improper access restrictions on CGI scripts in Red Hat Administration Server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-84ph-43p3-259x

## What is CVE-2008-0893?

CVE-2008-0893 is a high-severity missing authorization vulnerability in n/a, published on 16 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Red Hat Administration Server, as used by Red Hat Directory Server 8.0 EL4 and EL5, does not properly restrict access to CGI scripts, which allows remote attackers to perform administrative actions.

Weakness: CWE-264

## Which versions are affected by CVE-2008-0893?

It affects 1 product.


Products: Redhat Directory Server.

## How do I fix CVE-2008-0893?

Apply the vendor's patch.

## Is CVE-2008-0893 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2928](https://insights.sbomify.com/CVE-2008-2928/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-0892](https://insights.sbomify.com/CVE-2008-0892/): Command injection in n/a (critical 9.0)
- [CVE-2008-1677](https://insights.sbomify.com/CVE-2008-1677/): Memory corruption in n/a (high 7.5)
- [CVE-2008-0890](https://insights.sbomify.com/CVE-2008-0890/): Privilege escalation in n/a (medium 4.6)
- [CVE-2010-2241](https://insights.sbomify.com/CVE-2010-2241/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0893 and fix it if it is affected.

What it is: CVE-2008-0893 is a high-severity missing authorization vulnerability in n/a, published on 16 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-0893 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-2008-0893/ (Markdown: https://insights.sbomify.com/CVE-2008-0893/index.md)
```

## Sources

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

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