CVE-2014-7435
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 AJD Bail Bonds (aka com.onesolutionapps.ajdbailbondsandroid) application 1.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 AJD Bail Bonds Android application version 1.1 fails to validate X.509 certificates from SSL servers during HTTPS connections, allowing attackers to perform man-in-the-middle attacks by presenting malicious certificates. This enables server spoofing and interception of sensitive data transmitted between the app and backend servers.
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.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 AJD Bail Bonds app is installedOn the Android device, go to Settings > Apps > All Apps and search for 'AJD Bail Bonds' or 'Onesolutionapps Ajd Bail Bonds'. Alternatively, use ADB command: pm list packages | grep -i ajdAffected if The package 'com.onesolutionapps.ajdbailbonds' or similar AJD Bail Bonds package is present on the device
-
Verify the installed version is 1.1In Settings > Apps > All Apps > AJD Bail Bonds, check the version number under 'App info'. Or use ADB: dumpsys package <package_name> | grep versionNameAffected if The version displayed is exactly 1.1
-
Inspect the app for improper TrustManager implementationDecompile the APK (using apktool or similar) and examine Java/Smali files for custom TrustManager implementations. Search for 'TrustManager' keyword in the decompiled source. Check if validateServerCertificate or similar methods exist that bypass certificate validation. Look for implementations that return true unconditionally or catch CertificateException without proper validation.Affected if A TrustManager is implemented that accepts all certificates or does not properly validate the X.509 certificate chain
-
Check for missing certificate pinningExamine the decompiled APK source code for presence of CertificatePinning or SSLSocketFactory configurations. Search for certificate hash/pin definitions in resource files or hardcoded pin arrays. Search terms: 'pin', 'pinning', 'sha256', 'certificate' in network-related classes.Affected if No certificate pinning mechanism is found in the app code and the app makes HTTPS connections to backend servers
A user is affected if the AJD Bail Bonds Android app version 1.1 is installed and the app does not implement proper X.509 certificate validation or pinning for its HTTPS connections.
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 using Android's Certificate Pinning or a properly configured TrustManager that verifies the complete X.509 certificate chain.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2014-7435 — 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-7435 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