CVE-2017-8938
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 Radio Javan app 9.3.4 through 9.6.1 for iOS does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
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 Radio Javan iOS app versions 9.3.4 through 9.6.1 fails to validate X.509 certificates during SSL/TLS connections, allowing man-in-the-middle attackers to intercept traffic by presenting forged certificates and capture sensitive information transmitted between the app and server.
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= 9.3.4= 9.4= 9.4.1= 9.4.2= 9.4.3= 9.4.4= 9.4.5= 9.5= 9.5.1= 9.6= 9.6.1CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Check installed Radio Javan app versionOpen the iOS device Settings app, navigate to General > iPhone Storage (or iPad Storage), find Radio Javan in the app list, and note the version number displayed under the app name. Alternatively, open the App Store app, search for Radio Javan, and view the version information on the app page.Affected if The version displayed is 9.3.4, 9.4, 9.4.1, 9.4.2, 9.4.3, 9.4.4, 9.4.5, 9.5, 9.5.1, 9.6, or 9.6.1
-
Verify app version in app metadataOpen the Radio Javan iOS app, go to any settings or about section within the app, and look for a version/build number displayed. Compare this against the affected versions listed.Affected if The version shown matches any of the affected versions 9.3.4 through 9.6.1
-
Confirm active network usageLaunch the Radio Javan app and attempt to stream audio content or access any network-dependent feature (such as loading the radio player or playlist). This confirms the app is actively making outbound SSL/TLS connections.Affected if The app successfully connects to Radio Javan servers using SSL/TLS, meaning the vulnerable certificate validation code path is being exercised
You are affected if you have Radio Javan iOS app version 9.3.4 through 9.6.1 installed and actively use the app to connect to Radio Javan streaming services, allowing potential MITM attackers to intercept your traffic.
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 dataImplement proper SSL certificate validation in the app's networking layer by verifying the certificate chain, validating the hostname, and considering certificate pinning for critical endpoints.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8938 — 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-2017-8938 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