# CVE-2005-1709: Missing authorization in n/a

> Remote unauthenticated attackers can add licenses to Blue Coat Reporter due to missing authorization checks.

- **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:** 24 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q9x4-h529-9mpg

## What is CVE-2005-1709?

CVE-2005-1709 is a high-severity missing authorization vulnerability in n/a, published on 24 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unknown vulnerability in Blue Coat Reporter before 7.1.2 allows remote unauthenticated attackers to add a license.

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

It affects 1 product.


Products: Bluecoat Reporter.

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

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

## Is CVE-2005-1709 being exploited?

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

Public exploit code:

- Blue Coat Reporter 7.0/7.1 - License HTML Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-5127](https://insights.sbomify.com/CVE-2011-5127/): Path traversal in n/a (critical 10.0)
- [CVE-2005-1708](https://insights.sbomify.com/CVE-2005-1708/): Privilege escalation in n/a (medium 4.6)
- [CVE-2005-1710](https://insights.sbomify.com/CVE-2005-1710/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1709 is a high-severity missing authorization vulnerability in n/a, published on 24 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1709 exists.

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

## Sources

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

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