# CVE-2013-5959: Denial of service in n/a

> Remote attackers can cause denial of service in Blue Coat ProxySG by triggering excessive HTTP pre-fetch requests via recursive HTML links.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3vj2-4g5h-4v38

## What is CVE-2013-5959?

CVE-2013-5959 is a high-severity denial of service vulnerability in n/a, published on 28 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Blue Coat ProxySG before 6.2.14.1, 6.3.x, 6.4.x, and 6.5 before 6.5.2 allows remote attackers to cause a denial of service (memory consumption and dropped connections) via a recursive href in an HTML page, which triggers a large number of HTTP RW pipeline pre-fetch requests.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-5959?

It affects 2 products.


Products: Bluecoat Proxysg, Bluecoat Proxysgos.

## How do I fix CVE-2013-5959?

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

## Is CVE-2013-5959 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-5189](https://insights.sbomify.com/CVE-2010-5189/): Privilege escalation in n/a (critical 9.3)
- [CVE-2009-1211](https://insights.sbomify.com/CVE-2009-1211/): Security feature bypass in n/a (medium 5.8)
- [CVE-2010-5190](https://insights.sbomify.com/CVE-2010-5190/): Security feature bypass in n/a (medium 5.0)
- [CVE-2010-5192](https://insights.sbomify.com/CVE-2010-5192/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5959 and fix it if it is affected.

What it is: CVE-2013-5959 is a high-severity denial of service vulnerability in n/a, published on 28 Sep 2013. 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-2013-5959 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-2013-5959/ (Markdown: https://insights.sbomify.com/CVE-2013-5959/index.md)
```

## Sources

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

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