CyberSecBulletin
CVE-2024-24272NVD status: Analyzed

Dualsafe Password Manager: Insertion of Sensitive Information into Log File

CVE-2024-24272 is a high-severity insertion of sensitive information into log file vulnerability in Dualsafe Password Manager from Itopvpn, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 1.4.24 as the first without the flaw, so updating Dualsafe Password Manager to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.24% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Dualsafe Password Manager to 1.4.24 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
ItopvpnDualsafe Password Managerbefore 1.4.241.4.24

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by CISA (ADP).

Official description

An issue in iTop DualSafe Password Manager & Digital Vault before 1.4.24 allows a local attacker to obtain sensitive information via leaked credentials as plaintext in a log file that can be accessed by the local user without knowledge of the master secret.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How developers prevent this class of flaw

  • Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Remove debug log files before deploying the application into production.
  • Protect log files against unauthorized read/write.

More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Technical write-ups (may include proof of concept)

Recent Insertion of Sensitive Information into Log File vulnerabilities

Spotted an error? Tell us.