# CVE-2009-3474: Security feature bypass in n/a

> Attackers can misuse certificates for unintended purposes due to ignored KeyDescriptor attributes, weakening security in SAML implementations.

- **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:** Yes
- **Published:** 29 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-3474, GHSA-575w-rwc7-4259

## What is CVE-2009-3474?

CVE-2009-3474 is a high-severity vulnerability in n/a, published on 29 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSAML 2.x before 2.2.1 and XMLTooling 1.x before 1.2.1, as used by Internet2 Shibboleth Service Provider 2.x before 2.2.1, do not follow the KeyDescriptor element's Use attribute, which allows remote attackers to use a certificate for both signing and encryption when it is designated for just one purpose, potentially weakening the intended security application of the certificate.

Weakness: CWE-310

## Which versions are affected by CVE-2009-3474?

It affects 3 products.


Products: Internet2 Opensaml, Internet2 Shibboleth-Sp, Internet2 Xmltooling.

## How do I fix CVE-2009-3474?

Upgrade to a fixed version.

## Is CVE-2009-3474 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3476](https://insights.sbomify.com/CVE-2009-3476/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-6440](https://insights.sbomify.com/CVE-2013-6440/): Exposure of Sensitive Information to an Unauthorized Actor in OpenSAML (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3474 and fix it if it is affected.

What it is: CVE-2009-3474 is a high-severity vulnerability in n/a, published on 29 Sep 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-2009-3474 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-2009-3474/ (Markdown: https://insights.sbomify.com/CVE-2009-3474/index.md)
```

## Sources

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

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