VulnerabilityPublished 6 May 2024Updated 2 Aug 2024

CVE-2024-34538: passwordsafe · PRNG

Affects passwordsafeSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 8.13.9.26689 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.13.9.26689

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

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

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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 May 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 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

Upgrade de.mateso/passwordsafe to 8.13.9.26689.

Affected software

Product	Affected	Fixed in
Mavende.mateso/passwordsafe`pkg:maven/de.mateso/passwordsafe`Other threats	Affected <8.13.9.26689	Fixed in 8.13.9.26689

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, organizations should implement several specific mitigations: 1) Restrict network access to Mateso PasswordSafe servers by using firewalls and network segmentation to limit exposure to trusted hosts only. 2) Enforce strict access controls and multi-factor authentication on systems hosting the password manager to reduce the risk of unauthorized access. 3) Monitor logs and network traffic for unusual or suspicious activity that could indicate exploitation attempts. 4) Evaluate the cryptographic configurations and consider migrating to alternative password management solutions with stronger cryptographic standards if feasible. 5) Educate users and administrators about the risk and encourage prompt reporting of anomalies. 6) Prepare for rapid deployment of patches once available by maintaining up-to-date inventories and testing environments. 7) Consider encrypting backups and sensitive exports from the password manager with strong, independent cryptographic methods. These measures collectively reduce the attack surface and limit potential damage from exploitation.

Description

Mateso PasswordSafe through 8.13.9.26689 has Weak Cryptography.

Impact

The primary impact of CVE-2024-34538 is the potential compromise of confidentiality for sensitive credentials managed by Mateso PasswordSafe. Attackers exploiting this weakness could decrypt stored passwords or intercept sensitive data, leading to unauthorized access to user accounts and systems. This could result in credential theft, lateral movement within networks, and subsequent data breaches or espionage activities. Since password management tools often hold keys to multiple systems, the impact can cascade, affecting multiple organizational assets and increasing the risk of widespread compromise. The vulnerability does not affect integrity or availability directly, but the loss of confidentiality alone can have severe consequences for organizational security posture. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on this software are particularly at risk. The ease of exploitation (no authentication or user interaction required) and network accessibility further elevate the threat level.

CWE-338Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
Implementation
Use functions or hardware which use a hardware-based random number generation for all crypto. This is the recommended solution. Use CyptGenRandom on Windows, or hw_rand() on Linux.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
OWASP ASVS 4.0.3
V6.3.3 (opens in a new tab)
V6.3.2 (opens in a new tab)
V6.3.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

hansesecure.de/2023/02/schwachstelle-in-passwordsafe-mateso/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 04:47 UTC

WeaknessesCWE-338

Technical details

References

Community reviews

Related threats