CVE-2015-0277 is an authentication-bypass vulnerability in PicketLink before version 2.7.0. When processing a SAML assertion containing an AudienceRestriction, the PicketLink Service Provider did not verify that it was a member of the specified Audience element. An attacker could submit a crafted SAML assertion and cause the Service Provider to accept an assertion not intended for that relying party, enabling login as another user.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PicketLink SAML assertion audience-validation flaw that can enable a remote attacker to log in to a victim account.
PicketLink SAML assertion audience-validation flaw that can enable a remote attacker to log in to a victim account.
An authentication-bypass flaw in PicketLink caused by failure to validate the SAML assertion Audience condition, potentially enabling login as a victim.
A PicketLink flaw in which the service provider does not validate the Audience condition in a SAML assertion.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.