# CVE-2024-24272: Information disclosure in n/a

> A local attacker can read plaintext credentials from log files in iTop DualSafe Password Manager, exposing sensitive user data.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-wgr7-wrhm-vcmg

## What is CVE-2024-24272?

CVE-2024-24272 is a high-severity vulnerability in n/a, published on 21 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-24272?

It affects 1 product.


Products: Itopvpn Dualsafe Password Manager.

## How do I fix CVE-2024-24272?

No fix has been published for CVE-2024-24272 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-24272 being exploited?

There is no known exploitation of CVE-2024-24272 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-7326](https://insights.sbomify.com/CVE-2024-7326/): IObit DualSafe Password Manager BPL RTL120.BPL uncontrolled search path (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24272 and fix it if it is affected.

What it is: CVE-2024-24272 is a high-severity vulnerability in n/a, published on 21 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-24272 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-24272/ (Markdown: https://insights.sbomify.com/CVE-2024-24272/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24272
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24272
- OSV: https://osv.dev/vulnerability/CVE-2024-24272

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-24272/
Summaries are generated and may contain mistakes; the official description above is the record.