CVE-2019-13241 json
FlightCrew v0.9.2 and older are vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash)…
published 7y ago modified 4mo ago also EUVD-2019-4748
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
FlightCrew v0.9.2 and older are vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) in a ZIP archive entry that is mishandled during extraction.
Patch / fix
- flightcrew Debian 14, Debian 13, Debian 12 0.7.2+dfsg-14
debian advisories DEBIAN-CVE-2019-13241
- flightcrew Ubuntu 16.04 LTS 0.7.2+dfsg-6ubuntu0.1
- flightcrew Ubuntu 18.04 LTS 0.7.2+dfsg-10ubuntu0.1
ubuntu advisories UBUNTU-CVE-2019-13241
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2019-13241 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-13241 updated cvss 5.9
flightcrew: directory traversal allows to write arbitrary files
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.63% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/Sigil-Ebook/flightcrew/issues/52 referenced PoC, tagged "exploit" by a source, unverified
- salvatoresecurity.com https://salvatoresecurity.com/fun-with-fuzzers-how-i-discovered-three-vulnerabilities-part-3-of-3/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/Sigil-Ebook/flightcrew/issues/52
exploit, third-party-advisory
-
salvatoresecurity.com
/fun-with-fuzzers-how-i-discovered-three-vulnerabilities-part-3-of-3/
exploit, third-party-advisory
-
usn.ubuntu.com
/4055-1/
vendor-advisory, third-party-advisory
Sources
- CVE List CVE-2019-13241
- NVD CVE-2019-13241
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.