# CVE-2014-9749: Auth bypass in n/a

> Authenticated users can bypass access controls by replaying stale nonces when Digest authentication is enabled in Squid.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4g27-gq63-x5mg

## What is CVE-2014-9749?

CVE-2014-9749 is a medium-severity authentication bypass vulnerability in Opensuse Opensuse, published on 6 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Squid 3.4.4 through 3.4.11 and 3.5.0.1 through 3.5.1, when Digest authentication is used, allow remote authenticated users to retain access by leveraging a stale nonce, aka "Nonce replay vulnerability."

Weakness: CWE-264

## Which versions are affected by CVE-2014-9749?

It affects 2 products.


Products: Opensuse Opensuse, Squid-Cache Squid.

## How do I fix CVE-2014-9749?

Upgrade to a fixed version.

## Is CVE-2014-9749 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2015-5957](https://insights.sbomify.com/CVE-2015-5957/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-0491](https://insights.sbomify.com/CVE-2015-0491/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2388](https://insights.sbomify.com/CVE-2008-2388/): Integer overflow in n/a (critical 10.0)
- [CVE-2010-1866](https://insights.sbomify.com/CVE-2010-1866/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-0492](https://insights.sbomify.com/CVE-2015-0492/): Other in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9749 and fix it if it is affected.

What it is: CVE-2014-9749 is a medium-severity authentication bypass vulnerability in Opensuse Opensuse, published on 6 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9749 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-2014-9749/ (Markdown: https://insights.sbomify.com/CVE-2014-9749/index.md)
```

## Sources

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

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