Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2018-5387

HIGHFix: GoGentoOSS/SAMLBase@482cdf8

CVE-2018-5387 is a high-severity (CVSS 7.5) Improper Authentication vulnerability in wizkunde samlbase. 1 public exploit reference exists, so weaponization risk is real. O3 Security detects and blocks CVE-2018-5387 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

Wizkunde SAMLBase may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating…

Published
Jul 24, 2018
Updated
Jun 17, 2026
Affected
1 product
Patched
See advisory
Exploits
1 known

Description

Wizkunde SAMLBase may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.

Affected Products

1 product · 1 configurations
Application
samlbasewizkunde
< 1.4.2
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every wizkunde samlbase deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Fix

    Apply the wizkunde samlbase security patch or hotfix for CVE-2018-5387 on the affected version, following the vendor advisory for your exact build.

  3. Workarounds

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2018-5387 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2018-5387. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Wizkunde SAMLBase may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.
O3 Security · Runtime Protection

Is CVE-2018-5387 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2018-5387 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.