# CVE-2008-7250: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script via the User-Agent header in Sarg, potentially leading to code execution or security bypass.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/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:** 30 Dec 2009
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2008-7250, GHSA-2jm6-v38h-g4f5

## What is CVE-2008-7250?

CVE-2008-7250 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cross-site scripting (XSS) vulnerability in Squid Analysis Report Generator (Sarg) 2.2.4 allows remote attackers to inject arbitrary web script or HTML via a JavaScript onload event in the User-Agent header, which is not properly handled when displaying the Squid proxy log. NOTE: this issue exists because of an incomplete fix for CVE-2008-1168.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Pedro Lineu Orso Sarg.

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

Apply the vendor's patch.

## Is CVE-2008-7250 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7249](https://insights.sbomify.com/CVE-2008-7249/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7250 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2009. 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-2008-7250 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-2008-7250/ (Markdown: https://insights.sbomify.com/CVE-2008-7250/index.md)
```

## Sources

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

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