CVE-2014-6798
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 McMaster Marauders (aka com.weever.marauders) application 1.0.1 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 McMaster Marauders Android application 1.0.1 fails to verify X.509 certificates from SSL servers, allowing man-in-the-middle attackers to spoof servers using crafted certificates and intercept sensitive information transmitted by the app.
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.0.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
- 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 McMaster Marauders app is installedUse Android package manager: `adb shell pm list packages | grep -i mcmaster` or check device settings under Apps for 'Mcmaster Marauders' or 'Weeverapps Mcmaster Marauders'Affected if The package is found on the device, indicating the app is present and potentially in use
-
Determine the installed application versionRun `adb shell dumpsys package <package_name>` and look for versionName and versionCode, or view the app info in Settings > Apps > McMaster MaraudersAffected if VersionName equals 1.0.1 exactly, matching the vulnerable release
-
Check if the app transmits sensitive data over networkReview app functionality and network traffic logs (using a proxy like Burp or Charles) to see if the app sends user credentials, personal information, or other sensitive data to remote serversAffected if The app communicates sensitive information over HTTPS without proper certificate validation, making interception possible
-
Inspect network traffic for certificate validation failuresSet up a man-in-the-middle proxy with a self-signed certificate and attempt to intercept the app's traffic; observe if the app accepts the invalid certificate without warningAffected if The app accepts invalid or mismatched SSL certificates, confirming the certificate validation vulnerability is present
A user is affected if the McMaster Marauders Android app version 1.0.1 is installed and is used to transmit sensitive data over HTTPS connections without proper 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/TLS certificate validation including chain-of-trust verification, hostname validation, and revocation checking using Android's native TrustManager or network security configuration.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6798 — 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-6798 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