Dangerzone
Approved changes feed: RSS · Atom
cpe:2.3:a:freedom:dangerzone:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Freedom (7e8acd3a-1109-5a5d-8d30-b9700f0d0f12) |
|---|---|
| Product | Dangerzone (7f861708-7955-5b71-869b-9a033171b454) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/freedomofpress/dangerzone |
purl2cpe | 2026-06-01 10:14:03.427887 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-39342 |
vulnerable | 2026-06-08 06:09:37.159608 |
Dangerzone CLI does not sanitize ANSI escape characters
LOW (3.6)
Dangerzone is software for converting potentially dangerous PDFs, office documents, or images to safe PDFs. The Dangerzone CLI (`dangerzone-cli` command) logs output from the container where the file sanitization takes place, to the user's terminal. Prior to version 0.4.2, if the container is compromised and can return attacker-controlled strings, then the attacker may be able to spoof messages in the user's terminal or change the window title. Besides logging output from containers, it also logs the names of the files it sanitizes. If these files contain ANSI escape sequences, then the same issue applies. Dangerzone is predominantly a GUI application, so this issue should leave most of our users unaffected. Nevertheless, we always suggest updating to the newest version. This issue is fixed in Dangerzone 0.4.2.
Published: 2023-08-08T17:31:10.609Z
Updated: 2024-10-04T15:06:10.772Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.