Debian LinuxOperating system · Debian
CVE-2011-4625
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsimplesamlphp before 1.6.3 (squeeze) and before 1.8.2 (sid) incorrectly handles XML encryption which could allow remote attackers to decrypt or forge messages.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSimpleSAMLphp versions before 1.6.3 and 1.8.2 contain flaws in XML encryption handling that could allow remote attackers to decrypt encrypted SAML messages or forge authentication assertions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 8.0= 9.0= 10.0>= 1.6.0, < 1.6.3>= 1.8.0, < 1.8.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed SimpleSAMLphp versionLocate the SimpleSAMLphp installation directory and check the VERSION file or run 'php -r "require_once('lib/_autoload.php'); echo SimpleSAML_Configuration::getInstance()->getVersion();"' from the SimpleSAMLphp root directoryAffected if The version is 1.6.0 through 1.6.2, or 1.8.0 through 1.8.1 (versions prior to 1.6.3 or 1.8.2)
-
Check for SAML SP metadata configurationExamine the SimpleSAMLphp metadata directory (commonly ssp/config/metADATA or similar) for SAML Service Provider (SP) configuration files containing encrypted assertions or encryption keysAffected if SP is configured to receive encrypted SAML assertions using XML encryption
-
Verify IdP encryption settingsReview the identity provider (IdP) metadata configuration for any encryption certificates or keys configured for SAML message protectionAffected if IdP is configured to send encrypted SAML assertions to the SP
-
Inspect XML encryption module statusCheck the SimpleSAMLphp configuration file (config.php) for the 'enable.xmlsec' or 'secretsalt' settings and whether XML encryption functions are actively usedAffected if XML encryption functionality is enabled and processing incoming SAML messages
A user is affected if they run SimpleSAMLphp version 1.6.0-1.6.2 or 1.8.0-1.8.1 AND process encrypted SAML assertions from an IdP.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.6.31.8.2
Upgrade SimpleSAMLphp to version 1.6.3 or later (squeeze) or 1.8.2 or later (sid) to resolve the XML encryption handling vulnerability.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4625 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-4625 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data