CVE-2019-13032
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in FlightCrew v0.9.2 and earlier. A NULL pointer dereference occurs in GetRelativePathToNcx() or GetRelativePathsToXhtmlDocuments() when a NULL pointer is passed to xc::XMLUri::isValidURI(). This affects third-party software (not Sigil) that uses FlightCrew as a library.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA NULL pointer dereference vulnerability exists in FlightCrew v0.9.2 and earlier where the functions GetRelativePathToNcx() or GetRelativePathsToXhtmlDocuments() crash when a NULL pointer is passed to xc::XMLUri::isValidURI(). This affects third-party software using FlightCrew as a library.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.9.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate FlightCrew library in the environmentSearch for library files named 'FlightCrew', 'libFlightCrew', or similar patterns (.so on Linux, .dll/.lib on Windows, .dylib on macOS) in common system and application directoriesAffected if FlightCrew library files are found in the system or in application bundles
-
Determine the installed FlightCrew versionCheck the library's version metadata (file properties, embedded version string, or package manager record) and compare to the affected range (<= 0.9.2)Affected if The version is 0.9.2 or earlier
-
Identify applications using FlightCrew as a libraryScan application binaries or dependencies for linkage to FlightCrew library (look for imports of functions like GetRelativePathToNcx or GetRelativePathsToXhtmlDocuments in linked binaries)Affected if Software links against or embeds a vulnerable FlightCrew library version
-
Verify if affected functions are invoked with untrusted XML inputIf source code or binary analysis is possible, examine code paths where GetRelativePathToNcx() or GetRelativePathsToXhtmlDocuments() are called, particularly with XML content from external or untrusted sourcesAffected if The vulnerable functions are called and could receive NULL pointer arguments from XML processing
You are affected if FlightCrew library version 0.9.2 or earlier is present in your environment or bundled with any software you run, and that library processes EPUB/XML content that could trigger the NULL pointer dereference in the affected functions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a version newer than FlightCrew v0.9.2 when available, or add NULL pointer validation before calling isValidURI() in the affected functions when using the library.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13032 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13032 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data