# CVE-2008-0633: Memory corruption in n/a

> Remote attackers can cause a denial of service in Anon Proxy Server via a buffer overflow when authentication is enabled.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r9v8-vjgf-82h8

## What is CVE-2008-0633?

CVE-2008-0633 is a medium-severity memory corruption vulnerability in n/a, published on 6 Feb 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in Anon Proxy Server 0.102 and earlier, when user authentication is enabled, allows remote attackers to cause a denial of service (exception) via a user name with a large number of quotes, which triggers the overflow during escaping.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Anon Proxy Server Anon Proxy Server.

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

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

## Is CVE-2008-0633 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0633 exists.

Public exploit code:

- Anon Proxy Server 0.100/0.102 - Remote Authentication Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-6459](https://insights.sbomify.com/CVE-2007-6459/): Command injection in n/a (medium 6.8)
- [CVE-2007-6460](https://insights.sbomify.com/CVE-2007-6460/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0633 is a medium-severity memory corruption vulnerability in n/a, published on 6 Feb 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0633 exists.

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-0633/ (Markdown: https://insights.sbomify.com/CVE-2008-0633/index.md)
```

## Sources

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

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