Singular up to 4.3.0 /tmp temp file

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

A vulnerability was found in Singular up to 4.3.0. It has been classified as critical. This affects an unknown functionality of the file /tmp. The manipulation with an unknown input leads to a temp file vulnerability. CWE is classifying the issue as CWE-377. Creating and using insecure temporary files can leave application and system data vulnerable to attack. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to gain the privileges of other users via a procedure in a file under /tmp. NOTE: this CVE Record is about sdb.cc and similar files in the Singular interface that have predictable /tmp pathnames; this CVE Record is not about the lack of a safe temporary-file creation capability in the Singular language.

The weakness was disclosed 09/09/2022 as 1137. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-40299 since 09/09/2022. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 4.3.1 eliminates this vulnerability. Applying the patch 5f28fbf066626fa9c4a8f0e6408c0bb362fb386c 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 entry VDB-229069 is pretty similar.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 6.9

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

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

Exploitinginfo

Class: Temp file
CWE: CWE-377
CAPEC: 🔍
ATT&CK: 🔍

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: Singular 4.3.1
Patch: 5f28fbf066626fa9c4a8f0e6408c0bb362fb386c

Timelineinfo

09/09/2022 🔍
09/09/2022 +0 days 🔍
09/09/2022 +0 days 🔍
10/14/2022 +35 days 🔍

Sourcesinfo

Advisory: 1137
Status: Confirmed

CVE: CVE-2022-40299 (🔍)
See also: 🔍

Entryinfo

Created: 09/09/2022 09:00 AM
Updated: 10/14/2022 05:49 PM
Changes: 09/09/2022 09:00 AM (42), 10/14/2022 05:49 PM (11)
Complete: 🔍
Cache ID: 3:85D:40

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!