# CVE-2005-3495: Auth bypass in n/a

> Remote attackers can bypass authentication in Ar-blog by modifying cookies, leading to unauthorized access.

- **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:** No
- **Published:** 4 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r7gw-9vvq-w4x5

## What is CVE-2005-3495?

CVE-2005-3495 is a high-severity authentication bypass vulnerability in n/a, published on 4 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ar-blog 5.2 and earlier allows remote attackers to bypass authentication by modifying cookies.

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

It affects 1 product.


Products: Ar-Blog Ar-Blog.

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

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

## Is CVE-2005-3495 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2809](https://insights.sbomify.com/CVE-2006-2809/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-1893](https://insights.sbomify.com/CVE-2006-1893/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-0333](https://insights.sbomify.com/CVE-2006-0333/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-3494](https://insights.sbomify.com/CVE-2005-3494/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3495 is a high-severity authentication bypass vulnerability in n/a, published on 4 Nov 2005. 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-2005-3495 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-3495/ (Markdown: https://insights.sbomify.com/CVE-2005-3495/index.md)
```

## Sources

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

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