IO FinNet tss-lib up to 1.x hash risky encryption

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.
5.8$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in IO FinNet tss-lib up to 1.x. Affected by this vulnerability is an unknown functionality. Performing a manipulation of the argument hash results in an unknown weakness. This vulnerability is known as CVE-2022-47931. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in IO FinNet tss-lib up to 1.x. It has been classified as problematic. The manipulation of the argument hash with an unknown input leads to a unknown weakness. CWE is classifying the issue as CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. This is going to have an impact on confidentiality. The summary by CVE is:

IO FinNet tss-lib before 2.0.0 allows a collision of hash values.

The weakness was published 12/23/2022 as 369ec50be1437588a9733443bcb2f15b794601d4. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-47931 since 12/22/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600 for this issue.

Upgrading to version 2.0.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 369ec50be1437588a9733443bcb2f15b794601d4 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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.8
VulDB Meta Temp Score: 5.8

VulDB Base Score: 2.6
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.1
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Risky encryption
CWE: CWE-327 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: tss-lib 2.0.0
Patch: 369ec50be1437588a9733443bcb2f15b794601d4

Timelineinfo

12/22/2022 🔍
12/23/2022 +1 days 🔍
12/23/2022 +0 days 🔍
01/23/2023 +31 days 🔍

Sourcesinfo

Advisory: 369ec50be1437588a9733443bcb2f15b794601d4
Status: Confirmed

CVE: CVE-2022-47931 (🔍)
GCVE (CVE): GCVE-0-2022-47931
GCVE (VulDB): GCVE-100-216645

Entryinfo

Created: 12/23/2022 10:12
Updated: 01/23/2023 09:14
Changes: 12/23/2022 10:12 (42), 01/23/2023 09:14 (13)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!