dbcve.org
Rbb Speed TestApplication · Iid

CVE-2017-2278

MEDIUM · 5.9 CVSS v3.0 Published 2017-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The RBB SPEED TEST App for Android version 2.0.3 and earlier, RBB SPEED TEST App for iOS version 2.1.0 and earlier 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 confidence

The RBB SPEED TEST mobile apps for Android (v2.0.3 and earlier) and iOS (v2.1.0 and earlier) fail to validate X.509 certificates from SSL servers, allowing attackers to perform man-in-the-middle attacks by presenting forged certificates and intercepting sensitive data transmitted between the app and backend servers.

MitigationEnable proper SSL/TLS certificate validation in the app's network implementation, typically by ensuring default certificate verification is not disabled or by implementing certificate pinning for added security.

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
Rbb Speed TestApplication
Affected:all versions

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if RBB Speed Test app is installed
    Check device for app named 'RBB Speed Test' or 'Iid Rbb Speed Test'. On Android: Settings > Apps > All Apps. On iOS: check home screen or Settings > General > iPhone Storage.
    Affected if The app is present on the device.
  2. Determine installed app version
    Android: Go to Settings > Apps > RBB Speed Test > App info, note the version. iOS: Go to Settings > General > iPhone Storage > RBB Speed Test, tap to see version number.
    Affected if Android version is 2.0.3 or earlier, or iOS version is 2.1.0 or earlier.
  3. Inspect Android APK for disabled certificate validation
    Decompile the APK using apktool. Search source code for TrustManager implementations that bypass validation (e.g., empty KeyStore, custom TrustManager accepting all certs), or NetworkSecurityConfig allowing cleartext traffic, or WebView settings with setCertificateVerifyPolicy set to ACCEPT_ALL.
    Affected if Code contains custom TrustManager that accepts all certificates, or SSL validation is explicitly disabled via TrustManager or similar mechanism.
  4. Inspect iOS binary for disabled certificate validation
    Analyze the binary or source code (if available) for NSURLSessionConfiguration with TLSDisabled property set to true, or for custom URLSessionDelegate implementations that bypass certificate validation in didReceiveChallenge method.
    Affected if iOS code contains NSURLSessionConfiguration with TLS disabled or delegate methods that accept any server certificate.
  5. Test network behavior with MITM proxy
    Configure a proxy like Burp Suite or mitmproxy on the device network, install the proxy CA certificate, and attempt to capture traffic from the app. If traffic is decrypted and sensitive data is visible, certificate validation is not functioning properly.
    Affected if App traffic flows through the proxy without certificate warnings and sensitive data is readable in plain text.

The environment is affected if the RBB Speed Test app (Android v2.0.3 or earlier, iOS v2.1.0 or earlier) is installed AND the app's network code disables or bypasses SSL/TLS certificate validation, allowing decrypted MITM traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable proper SSL/TLS certificate validation in the app's network implementation, typically by ensuring default certificate verification is not disabled or by implementing certificate pinning for added security.

Fix this in Rbb Speed Test Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2278 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2278 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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