CVE-2019-11554
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 · uneditedThe Audible application through 2.34.0 for Android has Missing SSL Certificate Validation for Adobe SDKs, allowing MITM attackers to cause a denial of service.
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 confidenceThe Audible Android application through version 2.34.0 fails to validate SSL certificates when communicating with Adobe SDKs. This missing certificate validation allows man-in-the-middle attackers on the same network to intercept, manipulate, or block traffic between the app and Adobe services, resulting in denial of service.
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<= 2.34.0CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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.
-
Verify Audible Android app is installedOn the Android device, go to Settings > Apps > Applications Manager, or check the Google Play Store library, and look for Amazon Audible or Audible: Audiobooks & OriginalsAffected if The Amazon Audible Android application is present on the device
-
Determine the installed Audible app versionIn Settings > Apps > Audible, tap on App Info or App Details to view the version number. Alternatively, open the Google Play Store app, search for Audible, and view the version under Additional InformationAffected if Unable to determine the version number from the device or store listing
-
Compare version against CVE thresholdIf the version is displayed as a number (for example: 2.34.0, 2.33.5, 2.30.0), compare it numerically to 2.34.0. Any version equal to or lower than 2.34.0 is within the affected rangeAffected if The installed version number is 2.34.0 or lower (for example: 2.34.0, 2.33.0, 2.30.1, 2.25.0)
-
Confirm the app connects to Adobe servicesReview the Audible app functionality or network traffic (if using a proxy) to confirm the app communicates with Adobe-related services or SDKs, as this is the prerequisite condition for the SSL validation flaw to be relevantAffected if The app does not appear to communicate with Adobe services (in this case, the vulnerability may not be exploitable for that specific use case)
A user is affected if the Amazon Audible Android application version 2.34.0 or lower is installed and the app communicates with Adobe services, as this combination allows MITM attackers on the same network to intercept or manipulate traffic due to missing SSL certificate validation.
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 dataUpdate the Audible Android application to a version newer than 2.34.0 which should implement proper SSL certificate validation. If a newer version is unavailable, contact Amazon/Audible security for a patch.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11554 — 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-11554 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