# CVE-2012-4566: Auth bypass in n/a

> Remote attackers can bypass access restrictions and spoof clients in radsecproxy due to improper certificate verification in DTLS configurations.

- **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:** 20 Nov 2012
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-4566, GHSA-3qgg-3fwc-j9gv

## What is CVE-2012-4566?

CVE-2012-4566 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The DTLS support in radsecproxy before 1.6.2 does not properly verify certificates when there are configuration blocks with CA settings that are unrelated to the block being used for verifying the certificate chain, which might allow remote attackers to bypass intended access restrictions and spoof clients, a different vulnerability than CVE-2012-4523.

Weakness: CWE-264

## Which versions are affected by CVE-2012-4566?

It affects 1 product.


Products: Uninett Radsecproxy.

## How do I fix CVE-2012-4566?

Upgrade to a fixed version.

## Is CVE-2012-4566 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4523](https://insights.sbomify.com/CVE-2012-4523/): Auth bypass in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4566 and fix it if it is affected.

What it is: CVE-2012-4566 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Nov 2012. 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-2012-4566 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-2012-4566/ (Markdown: https://insights.sbomify.com/CVE-2012-4566/index.md)
```

## Sources

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

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