# CVE-2009-0788: Server-side request forgery in n/a

> Remote attackers can exploit improper URL rewriting to access sensitive host information or use the server as a proxy for arbitrary connections.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-688x-7w25-gh2x

## What is CVE-2009-0788?

CVE-2009-0788 is a medium-severity server-side request forgery vulnerability in n/a, published on 18 Apr 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Red Hat Network (RHN) Satellite Server 5.3 and 5.4 does not properly rewrite unspecified URLs, which allows remote attackers to (1) obtain unspecified sensitive host information or (2) use the server as an inadvertent proxy to connect to arbitrary services and IP addresses via unspecified vectors.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Redhat Network Satellite Server.

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

Apply the vendor's patch.

## Is CVE-2009-0788 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4139](https://insights.sbomify.com/CVE-2009-4139/): Cross-site request forgery in Red Hat Enterprise Linux 6 (medium 6.8)
- [CVE-2011-0717](https://insights.sbomify.com/CVE-2011-0717/): Auth bypass in n/a (medium 5.8)
- [CVE-2011-0718](https://insights.sbomify.com/CVE-2011-0718/): Auth bypass in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0788 is a medium-severity server-side request forgery vulnerability in n/a, published on 18 Apr 2011. 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-2009-0788 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-2009-0788/ (Markdown: https://insights.sbomify.com/CVE-2009-0788/index.md)
```

## Sources

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

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