CVE-2014-7439
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 bene+ odmeny a slevy (aka cz.gemoney.bene.android) application 1.2.3 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 Android application 'bene+ odmeny a slevy' version 1.2.3 fails to verify X.509 certificates from SSL/TLS servers. This improper certificate validation allows man-in-the-middle attackers to intercept encrypted communications by presenting a crafted (likely self-signed) certificate, enabling them to spoof the legitimate server and capture sensitive user data transmitted through 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.2.3CVSS 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 vulnerable app is installedOn the Android device, go to Settings > Apps > Downloaded, or use ADB command: 'adb shell pm list packages' and look for the package name associated with 'bene+ odmeny a slevy' or 'Beneplus Bene+ Odmeny A Slevy'Affected if The app is present on the device
-
Check the installed version numberIn Settings > Apps > [app name] > Version, or use ADB: 'adb shell dumpsys package [package_name]' to read the versionCode/versionNameAffected if The version is exactly 1.2.3 (versionCode matching 1.2.3 build)
-
Verify SSL certificate validation behaviorExtract the APK from the device (adb pull /data/app/[package_name].apk), then analyze the code for TrustManager implementation or certificate pinning using a decompiler (e.g., jadx). Search for classes implementing X509TrustManager and check if they properly validate the certificate chainAffected if The app uses a custom TrustManager that accepts all certificates, or implements no chain validation, or has no certificate pinning configured
You are affected if the app 'bene+ odmeny a slevy' version 1.2.3 is installed on your Android device and the APK lacks proper X.509 certificate chain validation or certificate pinning.
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 X.509 certificate validation in the Android application by using a custom TrustManager that validates the server certificate chain, or implement certificate pinning for known trusted certificates. All HTTPS connections should validate the certificate before establishing the secure channel.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7439 — 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-7439 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