Oniguruma before 6.9.3 allows Stack Exhaustion in regcomp.c because of recursion in regparse.c
Unknown · Unknown
7.5HighCVSS 3.1
Recommended action
Within 7 days
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 5 Aug 2024
Evidence used
No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 2.75% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
Release-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
4 package states
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
Distribution release
Source package
Vendor state
Fixed version
Evidence
Debian trixietrixie · source
libonig
Vendor fix publishedDebian records a fixed source-package version for this release.
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2019-6983
No EUVD known-exploited evidence
ENISA has published the identifier mapping but no EUVD description has been stored yet.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available
01
What, why and how
Oniguruma before 6.9.3 allows Stack Exhaustion in regcomp.c because of recursion in regparse.c.
What
Oniguruma before 6.9.3 allows Stack Exhaustion in regcomp.c because of recursion in regparse.c.
Why
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Oniguruma before 6.9.3 allows Stack Exhaustion in regcomp.c because of recursion in regparse.c.
Why
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
Likely attack path
a network path → Uncontrolled Recursion → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-674: Uncontrolled Recursion. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2019-6983Official EUVD mapping
0 linked advisory records.
Official EUVD record ↗BSI · German · WID-SEC-2024-1086IBM QRadar SIEM: Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, Dateien zu manipulieren, seine Privilegien zu erweitern, einen Cross-Site-Scripting (XSS)-Angriff durchzuführen oder einen nicht spezifizierten Angriff auszuführen.
Official advisory ↗BSI · German · WID-SEC-2024-0218Red Hat Enterprise Linux's oniguruma, tcpslice, c-ares: Mehrere Schwachstellen
Ein entfernter Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, beliebigen Code auszuführen oder sensible Informationen offenzulegen.
Official advisory ↗CERT-FR · French · CERTFR-2025-AVI-0337Multiples vulnérabilités dans les produits IBM
r au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Documentation
Bulletin de sécurité IBM 7230739 du 11 avril 2025
https://www.ibm.com/support/pages/node/7230739
Bulletin de sécurité IBM 7231051 du 16 avril 2025
https://www.ibm.com/support/pages/node/7231051
Bulletin de sécurité IBM 7231169 du 17 avril 2025
https://www.ibm.com/support/pages/node/7231169
Référence CVE CVE-2018-12699
https://www.cve.org/CVERecord?id=CVE-2018-12699
Référence CVE CVE-2018-18700
https://www.cve.org/CVERecord?id=CVE-2018-18700
Référence CVE CVE-2019-12972
https://www.cve.org/CVERecord?id=CVE-2019-12972
Référence CVE CVE-2019-16163
https://www.cve.org/CVERecord?id=CVE-2019-16163
Référence CVE CVE-2020-15250
https://www.cve.org/CVERecord?id=CVE-2020-15250
Référence CVE CVE-2020-35493
https://www.cve.org/CVERecord?id=CVE-2020-35493
Référence CVE CVE-2020-35494
https://www.cve.org/CVERecord?id=CVE-2020-35494
Référence CVE CVE-2020-35495
https://www.cve.org/CVERecord?id=CVE-2020-35495
Référence CVE CVE-2020-35496
https://www.cve.org/CVERecord?id=CVE-2020-35496
Référence CVE CVE-2020-35507
https://www.cve.org/CVERecord?id=CVE-2020-35507
Référence CVE CVE-2023-1370
https://www.cve.org/CVERecord?id=CVE-2023-1370
Référence CVE CVE-2023-1972
https://www.cve.org/CVERecord?id=CVE
Official advisory ↗CERT-FR · French · CERTFR-2024-AVI-0923Multiples vulnérabilités dans les produits IBM
re 2024
https://www.ibm.com/support/pages/node/7173866
Bulletin de sécurité IBM 7174015 du 24 octobre 2024
https://www.ibm.com/support/pages/node/7174015
Bulletin de sécurité IBM 7174016 du 24 octobre 2024
https://www.ibm.com/support/pages/node/7174016
Référence CVE CVE-2012-2677
https://www.cve.org/CVERecord?id=CVE-2012-2677
Référence CVE CVE-2018-12538
https://www.cve.org/CVERecord?id=CVE-2018-12538
Référence CVE CVE-2018-12545
https://www.cve.org/CVERecord?id=CVE-2018-12545
Référence CVE CVE-2019-10241
https://www.cve.org/CVERecord?id=CVE-2019-10241
Référence CVE CVE-2019-13224
https://www.cve.org/CVERecord?id=CVE-2019-13224
Référence CVE CVE-2019-16163
https://www.cve.org/CVERecord?id=CVE-2019-16163
Référence CVE CVE-2019-19012
https://www.cve.org/CVERecord?id=CVE-2019-19012
Référence CVE CVE-2020-15168
https://www.cve.org/CVERecord?id=CVE-2020-15168
Référence CVE CVE-2020-27216
https://www.cve.org/CVERecord?id=CVE-2020-27216
Référence CVE CVE-2021-28169
https://www.cve.org/CVERecord?id=CVE-2021-28169
Référence CVE CVE-2021-34428
https://www.cve.org/CVERecord?id=CVE-2021-34428
Référence CVE CVE-2021-3803
https://www.cve.org/CVERecord?id=CVE-2021-3803
Référence CVE CVE-2021-40690
https://www.cve.org/CVERecord?id=CVE-2021-40690
Référence CVE CVE-2021-43138
https://www.cve.org/CVERecord?id=CV
Official advisory ↗CERT-FR · French · CERTFR-2024-AVI-0506Multiples vulnérabilités dans Juniper Secure Analytics
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 9 Sept 2019 · Last source change 5 Aug 2024, 01:10 UTC · CWE-674 · Uncontrolled Recursion
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2019-6983
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
Affected versionsThe structured affected or fixed version information changed.
Before
n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.