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

CVE-2012-5575

CVE-2012-5575 is a CWE-310 vulnerability in apache cxf. O3 Security detects and blocks CVE-2012-5575 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

Apache CXF 2.5.x before 2.5.10, 2.6.x before CXF 2.6.7, and 2.7.x before CXF 2.7.4 does not verify that a specified cryptographic algorithm is allowed by the WS-SecurityPolicy AlgorithmSuite…

Published
Aug 19, 2013
Updated
Jun 16, 2026
Affected
0 pkgs
Patched
None yet
Exploits
None indexed

Description

Apache CXF 2.5.x before 2.5.10, 2.6.x before CXF 2.6.7, and 2.7.x before CXF 2.7.4 does not verify that a specified cryptographic algorithm is allowed by the WS-SecurityPolicy AlgorithmSuite definition before decrypting, which allows remote attackers to force CXF to use weaker cryptographic algorithms than intended and makes it easier to decrypt communications, aka "XML Encryption backwards compatibility attack."

Affected Products

6 products · 26 configurations
Application
cxfapache
21 versions
2.5.02.5.12.5.22.5.32.5.42.5.52.5.62.5.72.5.82.5.92.6.02.6.1
Application
jboss enterprise application platformredhat
1 version
5.0.0
Application
jboss enterprise portal platformredhat
1 version
4.3.0
Application
jboss enterprise soa platformredhat
1 version
4.3.0
Application
jboss enterprise web platformredhat
1 version
5.2.0
Application
jboss fuse esb enterpriseredhat
1 version
7.1.0

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every apache cxf 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. Remediation status

    No patch has shipped for CVE-2012-5575 yet — track the apache cxf advisory for a fixed release and apply the workarounds below in the meantime.

  3. Mitigate without a patch

    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-2012-5575 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-2012-5575. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Apache CXF 2.5.x before 2.5.10, 2.6.x before CXF 2.6.7, and 2.7.x before CXF 2.7.4 does not verify that a specified cryptographic algorithm is allowed by the WS-SecurityPolicy AlgorithmSuite definition before decrypting, which allows remote attackers to force CXF to use weaker cryptographic algorithms than intended and makes it easier to decrypt communications, aka "XML Encryption backwards compatibility attack."
O3 Security · Runtime Protection

Is CVE-2012-5575 being exploited in your environment?

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