CVE-2009-3476: Buffer overflow in OpenSAML before 1.1.3 as used in Internet2 Shibboleth Service Provider software 1.3.x before 1.3.4, and XMLTooling before…
Noroxi assessment
Priority: Monitor (action score 38/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.1% (FIRST EPSS); higher than 90.9% of all records.
- Fixed version: opensaml (Debian:12) 3.0.0-2; shibboleth-sp (Debian:12) 3.0.2+dfsg1-2; xmltooling (Debian:12) 1.2.2-1.
Low priority for now. Upgrade to opensaml (Debian:12) 3.0.0-2; shibboleth-sp (Debian:12) 3.0.2+dfsg1-2; xmltooling (Debian:12) 1.2.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Buffer overflow in OpenSAML before 1.1.3 as used in Internet2 Shibboleth Service Provider software 1.3.x before 1.3.4, and XMLTooling before 1.2.2 as used in Internet2 Shibboleth Service Provider software 2.x before 2.2.1, allows remote attackers to cause a denial of service and possibly execute arbitrary code via a malformed encoded URL.
- Published
- Sep 29, 2009
- Updated
- Jun 16, 2026
- EPSS
- 4.1% · 90th percentile
- CWE
- CWE-119
Report tools
Action score
38
Low priority for now.
- CVSS
- 37 / 40 · 9.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| internet2 | shibboleth-sp | cpe:2.3:a:internet2:shibboleth-sp |
| internet2 | opensaml | cpe:2.3:a:internet2:opensaml |
| internet2 | xmltooling | cpe:2.3:a:internet2:xmltooling |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- internet2 opensaml1.1
- internet2 opensaml1.1.1
- internet2 shibboleth-sp1.3.1
- internet2 shibboleth-sp1.3.2
- internet2 shibboleth-sp1.3.3
- internet2 shibboleth-sp1.3f
- internet2 shibboleth-sp2.0
- internet2 shibboleth-sp2.1
+6 more rows
- internet2 shibboleth-sp2.2
- internet2 xmltooling1.0.1
- internet2 xmltooling1.1.0
- internet2 xmltooling1.1.1
- internet2 xmltooling1.2.0
- internet2 xmltooling1.2.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | opensaml | before 3.0.0-2 | 3.0.0-2 |
| Debian:12 | shibboleth-sp | before 3.0.2+dfsg1-2 | 3.0.2+dfsg1-2 |
| Debian:12 | xmltooling | before 1.2.2-1 | 1.2.2-1 |
| Debian:4.0 | opensaml | before 1.1a-2+etch1 | 1.1a-2+etch1 |
| Debian:4.0 | shibboleth-sp | before 1.3f.dfsg1-2+etch1 | 1.3f.dfsg1-2+etch1 |
| Debian:5.0 | opensaml | before 1.1.1-2+lenny1 | 1.1.1-2+lenny1 |
| Debian:5.0 | opensaml2 | before 2.0-2+lenny1 | 2.0-2+lenny1 |
| Debian:5.0 | shibboleth-sp | before 1.3.1.dfsg1-3+lenny1 | 1.3.1.dfsg1-3+lenny1 |
| Debian:5.0 | shibboleth-sp2 | before 2.0.dfsg1-4+lenny1 | 2.0.dfsg1-4+lenny1 |
| Debian:5.0 | xmltooling | before 1.0-2+lenny1 | 1.0-2+lenny1 |
Same product
internet2: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-3475Internet2 Shibboleth Service Provider software 1.3.x before 1.3.3 and 2.x before 2.2.1, when using PKIX trust validation, does not properly…30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:opensaml | 3.0.0-2 · Debian:12 | Package registry (OSV) |
| debian:opensaml2 | 2.0-2+lenny1 · Debian:5.0 | Package registry (OSV) |
| debian:shibboleth-sp | 3.0.2+dfsg1-2 · Debian:12 | Package registry (OSV) |
| debian:shibboleth-sp2 | 2.0.dfsg1-4+lenny1 · Debian:5.0 | Package registry (OSV) |
| debian:xmltooling | 1.2.2-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:M/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.