S-Lang 2.3.2 tt_sprintf improper check or handling of exceptional conditions

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

Summaryinfo

A vulnerability, which was classified as problematic, was found in S-Lang 2.3.2. This issue affects the function tt_sprintf. Such manipulation leads to an unknown weakness. This vulnerability is uniquely identified as CVE-2023-45927. No exploit exists.

Detailsinfo

A vulnerability was found in S-Lang 2.3.2 and classified as problematic. Using CWE to declare the problem leads to CWE-703. The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product. The impact remains unknown. CVE summarizes:

S-Lang 2.3.2 was discovered to contain an arithmetic exception via the function tt_sprintf().

The weakness was disclosed 01/26/2024. The advisory is shared for download at seclists.org. This vulnerability is handled as CVE-2023-45927 since 10/16/2023. There are known technical details, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.2

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 9.1
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Improper check or handling of exceptional conditions
CWE: CWE-703
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/16/2023 🔍
01/26/2024 +102 days 🔍
01/26/2024 +0 days 🔍
05/31/2025 +491 days 🔍

Sourcesinfo

Advisory: seclists.org
Status: Not defined

CVE: CVE-2023-45927 (🔍)
GCVE (CVE): GCVE-0-2023-45927
GCVE (VulDB): GCVE-100-252212

Entryinfo

Created: 01/26/2024 19:52
Updated: 05/31/2025 05:34
Changes: 01/26/2024 19:52 (34), 08/07/2024 01:28 (27), 05/31/2025 05:34 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!