michaelliao jopenid prior 1.08 OpenIdManager.java getAuthentication timing discrepancy
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
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 with an unknown input leads to a timing discrepancy vulnerability. CWE is classifying the issue as CWE-208. Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not. This is going to have an impact on confidentiality.
The weakness was published 01/17/2023 as c9baaa976b684637f0d5a50268e91846a7a719ab. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2010-10006. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
Upgrading to version 1.08 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch c9baaa976b684637f0d5a50268e91846a7a719ab is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The advisory contains the following remark:
fix timing vulnerability.
CVSSv3VulDB Meta Base Score: 2.6
VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.6
VulDB Temp Score: 2.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Timing discrepancy
CWE: CWE-208 / CWE-203 / CWE-200
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: jopenid 1.08
Timeline01/16/2023 VulDB entry created
01/17/2023 +0 days Advisory disclosed
01/17/2023 +0 days VulDB last update
CVE: CVE-2010-10006 (🔒)
EntryCreated: 01/17/2023 12:05 AM
Changes: 01/17/2023 12:05 AM (44)
Do you want to use VulDB in your project?
Use the official API to access entries easily!