Skip to main content
CVE-2023-4641VulnerabilityPublished Updated

CVE-2023-4641: Incorrect Implementation of Authentication Algorithm

Source CVE Database V5

0

Not known to be exploited · CVSS 4.7 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Dec 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2023-4641, organizations should monitor for and apply security patches from their Linux distribution vendors as soon as they become available. In the interim, restrict local access to trusted users only, minimizing the risk of an attacker gaining the necessary access to exploit this vulnerability. Employ strict user privilege separation and auditing to detect unauthorized access attempts. Consider using memory protection mechanisms and tools that can detect or prevent unauthorized memory reads. Additionally, educate system administrators and users about the risks of password management vulnerabilities and encourage the use of multi-factor authentication to reduce the impact of credential compromise. Regularly review and harden system configurations to limit local access vectors, and implement monitoring solutions to detect suspicious activities related to password changes or memory access.

Description

A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.

References

Community reviews

Loading reviews…