# CVE-2003-0493: Auth bypass in n/a

> Attackers can hijack user sessions by stealing and replaying encrypted passwords, leading to unauthorized access and privilege escalation in Snitz Forums.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-m4f4-g7p6-xr6g

## What is CVE-2003-0493?

CVE-2003-0493 is a critical authentication bypass vulnerability in n/a, published on 28 Jun 2003. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Snitz Forums 3.4.03 and earlier allows attackers to gain privileges as other users by stealing and replaying the encrypted password after obtaining a valid session ID.

## Which versions are affected by CVE-2003-0493?

It affects 1 product.


Products: Snitz Communications Snitz Forums 2000.

## How do I fix CVE-2003-0493?

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

## Is CVE-2003-0493 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0494](https://insights.sbomify.com/CVE-2003-0494/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-5603](https://insights.sbomify.com/CVE-2006-5603/): SQL injection in n/a (critical 9.8)
- [CVE-2012-5313](https://insights.sbomify.com/CVE-2012-5313/): SQL injection in n/a (high 7.5)
- [CVE-2010-4826](https://insights.sbomify.com/CVE-2010-4826/): SQL injection in n/a (high 7.5)
- [CVE-2007-6240](https://insights.sbomify.com/CVE-2007-6240/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0493 and fix it if it is affected.

What it is: CVE-2003-0493 is a critical authentication bypass vulnerability in n/a, published on 28 Jun 2003. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2003-0493 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-2003-0493/ (Markdown: https://insights.sbomify.com/CVE-2003-0493/index.md)
```

## Sources

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

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