VulnerabilityPublished 27 Mar 2024Updated 4 Nov 2025

CVE-2023-45927: S-Lang · Improper Check or Handling of Exceptional Conditions

Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Immediate identification of all systems running S-Lang 2.3.2 or incorporating it as a dependency is critical.
Apply patches or updates from the S-Lang maintainers as soon as they are released; monitor official channels for announcements.
If patches are unavailable, implement network-level protections such as firewall rules or intrusion prevention systems to restrict access to services using S-Lang, especially from untrusted networks.
Employ application-level input validation and sanitization to prevent triggering the arithmetic exception in tt_sprintf().
Monitor logs and system behavior for crashes or anomalies related to S-Lang processes to detect potential exploitation attempts early.
Consider isolating or sandboxing applications using S-Lang to limit the impact of a potential DoS.
Engage with vendors or internal developers to assess the use of S-Lang and plan for migration to safer alternatives if feasible.
Conduct security awareness and incident response training focused on recognizing and responding to DoS conditions caused by this vulnerability.

Description

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

Impact

For European organizations, the primary impact of CVE-2023-45927 is the potential for denial of service attacks that can disrupt critical services relying on S-Lang 2.3.2. This can affect telecommunications, industrial control systems, network monitoring tools, and other infrastructure components where S-Lang is embedded. The high CVSS score indicates a serious risk to availability and confidentiality, as service outages could lead to operational downtime and potential exposure of sensitive information if systems fail unpredictably. Organizations in sectors such as energy, finance, healthcare, and government may face increased risk due to their reliance on stable and secure infrastructure. The lack of required authentication and user interaction lowers the barrier for attackers, increasing the likelihood of exploitation attempts. Although no exploits are currently known, the vulnerability's presence in foundational libraries means that widespread impact is possible if attackers develop weaponized code. European entities must consider the risk of cascading failures in interconnected systems and the potential for targeted attacks leveraging this vulnerability.

CWE-703Improper Check or Handling of Exceptional Conditions (opens in a new tab)
Pillar weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2025, 18:56 UTC

WeaknessesCWE-703

Technical details

References

Community reviews

Related threats