Security Resilience

CVE-2023-45927

Jedsoft S-Lang 2.3.2

Published
27 March 2024
Modified
04 November 2025
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS Score 0.0084 57th percentile
Risk Priority 68 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-45927 is a critical-severity Improper Check or Handling of Exceptional Conditions (CWE-703) vulnerability in Jedsoft S-Lang. Its CVSS base score is 9.1 (Critical).

Operationally, ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-24 (Fail in Known State) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-703

Related Threats

CVEs Like This One

CVE-2023-45929Same product: Jedsoft S-Lang
CVE-2026-47316Shared CWE-703
CVE-2026-16218Shared CWE-703
CVE-2023-32230Shared CWE-703
CVE-2024-21629Shared CWE-703
CVE-2024-37992Shared CWE-703
CVE-2026-71640Shared CWE-703
CVE-2024-39514Shared CWE-703
CVE-2025-13016Shared CWE-703
CVE-2026-29643Shared CWE-703

Affected Assets

jedsoft
s-lang
2.3.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-24 Fail in Known State good match

Enforces failure to a known state while preserving required properties, limiting impact of unhandled exceptions.

SI-17 Fail-safe Procedures good match

Mandates explicit fail-safe procedures triggered by indicated failures, structurally preventing unhandled exceptional conditions.

SA-8 Security and Privacy Engineering Principles partial match

Requires application of security engineering principles that include robust exception and error handling during design.

SI-11 Error Handling partial match

Requires generation of safe, actionable error messages that directly addresses proper handling of exceptional conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.26 Application security requirements partial match
removes

A.8.26 only requires that security requirements (including resilience against attacks like SQL injection) be identified and specified during development or acquisition; it does not itself remove, fix, or eliminate any exceptional-condition handling defects already present in code.

A.8.28 Secure coding partial match
removes

A.8.28 mandates secure coding practices, principles, defect removal during coding/review, and prohibiting insecure techniques that directly produce improper exception handling; this removes most instances of the first-party code defect, with a bounded remainder in incomplete adoption or edge-case defects not captured by the baseline.

A.8.9 Configuration management partial match
removes

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-703, a pillar-level weakness, and none of its children carries one either.

References