# CVE-2009-0795: DO NOT USE THIS CANDIDATE NUMBER.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Apr 2009
- **Updated:** 16 Sep 2024

## What is CVE-2009-0795?

CVE-2009-0795 is a vulnerability, published on 8 Apr 2009. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2009-0796, CVE-2009-1265.  Reason: this candidate was intended for one issue, but a typo caused it to be associated with a different issue.  Notes: All CVE users should consult CVE-2009-0796 and CVE-2009-1265 to determine which ID is appropriate.  All references and descriptions in this candidate have been removed to prevent accidental usage

## Which versions are affected by CVE-2009-0795?


## How do I fix CVE-2009-0795?

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

## Is CVE-2009-0795 being exploited?

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

Public exploit code:

- Apache mod_perl - 'Apache::Status' / 'Apache2::Status' Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0795 and fix it if it is affected.

What it is: CVE-2009-0795 is a vulnerability, published on 8 Apr 2009. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0795 exists.

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

## Sources

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

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