How severe is CVE-2010-10006?

CVE-2010-10006 has a CVSS score of 2.6/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which products are affected by CVE-2010-10006?

Affected package information for CVE-2010-10006 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2010-10006?

Apply the jopenid_project jopenid security patch or hotfix for CVE-2010-10006 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2010-10006 across my infrastructure?

Inventory every jopenid_project jopenid 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.

How do I mitigate CVE-2010-10006 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2010-10006?

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

Is CVE-2010-10006 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-10006 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2010-10006?

CVE-2010-10006 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 54th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2010-10006?

CVE-2010-10006 is classified as CWE-208 (CWE-208), CWE-203 (CWE-203). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2010-10006?

CVE-2010-10006 affects jopenid_project jopenid. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2010-10006 published, and has it been updated?

CVE-2010-10006 was published on January 18, 2023 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2010-10006: Jopenid CWE-208 (Low 2.6)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk54th percentile+0.43%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

A vulnerability, which was classified as problematic, was found in michaelliao jopenid. Affected is the function getAuthentication of the file JOpenId/src/org/expressme/openid/OpenIdManager.java. The manipulation leads to observable timing discrepancy. The complexity of an attack is rather high. The exploitability is told to be difficult. Upgrading to version 1.08 is able to address this issue. The name of the patch is c9baaa976b684637f0d5a50268e91846a7a719ab. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-218460.

Affected Products

1 product · 1 configurations

Application

jopenidjopenid_project

< 1.08

range

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every jopenid_project jopenid 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.
Fix
Apply the jopenid_project jopenid security patch or hotfix for CVE-2010-10006 on the affected version, following the vendor advisory for your exact build.
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.
How O3 protects you
O3 detects and blocks CVE-2010-10006 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-2010-10006. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability, which was classified as problematic, was found in michaelliao jopenid. Affected is the function getAuthentication of the file JOpenId/src/org/expressme/openid/OpenIdManager.java. The manipulation leads to observable timing discrepancy. The complexity of an attack is rather high. The exploitability is told to be difficult. Upgrading to version 1.08 is able to address this issue. The name of the patch is c9baaa976b684637f0d5a50268e91846a7a719ab. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-218460.

O3 Security · Runtime Protection

Is CVE-2010-10006 being exploited in your environment?

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

Protect my workloads How runtime protection works

CVE-2010-10006

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2010-10006 being exploited in your environment?