CVE-2023-6681: Red Hat Enterprise Linux 8 · Uncontrolled Resource Consumption
Affects Red Hat Enterprise Linux 8Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% 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:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 12 Feb 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.
What to do
AI-suggested
European organizations should implement the following specific mitigations: 1) Monitor system resource usage closely, especially CPU and memory consumption related to cryptographic operations, to detect abnormal spikes indicative of exploitation attempts. 2) Apply rate limiting and throttling on authentication mechanisms to reduce the feasibility of brute-force and dictionary attacks that could trigger excessive resource consumption. 3) Deploy network-level protections such as intrusion detection/prevention systems (IDS/IPS) to identify and block suspicious traffic patterns targeting cryptographic services. 4) Maintain up-to-date patch management processes and apply Red Hat vendor patches promptly once available to address this vulnerability directly. 5) Consider isolating critical services running JWCrypto in controlled environments with resource quotas to limit the impact of potential DoS attacks. 6) Conduct regular security assessments and penetration testing focusing on authentication and cryptographic components to identify weaknesses. 7) Educate system administrators about this vulnerability and encourage vigilant monitoring of logs and alerts related to authentication failures and resource exhaustion. These targeted actions go beyond generic advice by focusing on the specific nature of the vulnerability and its exploitation vectors.
Description
A vulnerability was found in JWCrypto. This flaw allows an attacker to cause a denial of service (DoS) attack and possible password brute-force and dictionary attacks to be more resource-intensive. This issue can result in a large amount of computational consumption, causing a denial of service attack.