CVE-2014-5931
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 Stop & Shop SCAN IT! Mobile (aka com.modivmedia.scanitss) application 7.21.00 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 Stop & Shop SCAN IT! Mobile Android application version 7.21.00 fails to validate X.509 certificates when establishing SSL/TLS connections with servers. This allows an attacker positioned on the same network to intercept and modify traffic by presenting a fraudulent certificate, enabling credential theft, session hijacking, and injection of malicious content.
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= 7.21.00CVSS 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 installed app versionOn the Android device, go to Settings > Apps > Stop & Shop Scan It! Mobile and view the Version information, or run: adb shell dumpsys package com.stopandshop.scanitmobile | grep versionNameAffected if The version shown is 7.21.00 exactly, indicating the vulnerable version is installed
-
Confirm app handles sensitive dataReview app functionality: check if it is used for account login, storing payment credentials, viewing purchase history, or accessing loyalty program data that could be interceptedAffected if The app processes user credentials, payment information, or personal shopping data over the network
-
Verify network traffic inspection capabilityUse a network proxy (such as Burp Suite or OWASP ZAP) configured as the device's proxy, or use Android network debugging tools to observe if the app accepts the proxy's certificate without validation errorsAffected if The app successfully establishes SSL/TLS connections through an intercepting proxy without certificate validation errors, indicating lack of proper certificate validation
-
Check for enterprise mobile security controlsIf deployed in an enterprise environment, verify through MDM/Mobile Threat Defense solutions whether certificate pinning or network traffic inspection is enforced for this applicationAffected if No certificate pinning or additional security controls are enforced, and the app uses direct network connections
You are affected if the Stop & Shop Scan It! Mobile app version 7.21.00 is installed and processes sensitive user data over network connections without certificate validation or pinning protections in place.
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 dataThe application must implement proper SSL certificate validation, preferably through certificate pinning or at minimum proper X.509 chain verification using the Android TrustManager. All network communications should be re-tested to ensure sensitive data is not intercepted.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5931 — 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-5931 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