CVE-2014-6999
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 Questoes OAB (aka com.pedefeijao.questoesoab) application oab_android_1.2 for Android 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 Questoes OAB Android application (version oab_android_1.2) fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept and modify traffic by presenting forged certificates.
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= 1.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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/AC:M/Au:N/C:P/I:P/A:P
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.
-
Identify if the Questoes OAB app is installedOn the Android device, go to Settings > Apps or use a package manager to list installed applications. Look for an app named 'Jogoeusei Questoes Oab' or 'Questoes OAB'.Affected if The app with either of these names is present on the device
-
Verify the installed version is 1.2In the Android device's app settings (Settings > Apps > [App Name]), view the version information under 'App info' or 'Version'. Alternatively, use a command like 'adb shell dumpsys package [package_name]' to retrieve version details.Affected if The reported version number equals exactly 1.2
-
Confirm the app uses network communicationReview the app's functionality to determine if it sends or receives data over the network. This can be observed via network traffic monitoring or by checking app permissions for network access.Affected if The app transmits data over HTTP/HTTPS connections
-
Determine if SSL certificate validation is bypassedPerform dynamic analysis by intercepting network traffic using a proxy (such as Burp Suite or OWASP ZAP) with a self-signed certificate. Attempt to intercept HTTPS traffic from the app. If the app accepts the forged certificate without warning, certificate validation is not properly implemented.Affected if The app accepts an invalid or self-signed certificate during MITM proxy interception without presenting security warnings
The environment is affected if the Questoes OAB Android app version 1.2 is installed and it accepts invalid SSL certificates during network communications, indicating missing X.509 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 dataImplement proper SSL certificate validation using certificate pinning or standard X.509 verification with trusted CA stores in the Android application.
- Consultation2.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,400.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6999 — 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-2014-6999 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