CVE-2014-5843
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 ADP AGENCY Immobiliare (aka com.wAdpagencyAndroid) application 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 ADP AGENCY Immobiliare Android application version 0.1 fails to validate X.509 certificates from SSL servers during HTTPS connections. This classic SSL/TLS certificate validation vulnerability allows man-in-the-middle attackers to intercept encrypted communications by presenting forged certificates, enabling theft of sensitive data 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= 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 the installed applicationCheck if the Adp4u Adp Agency Immobiliare app is installed on the Android device. Go to Settings > Apps and look for 'ADP AGENCY Immobiliare' or 'Adp4u Adp Agency Immobiliare'.Affected if The app is present on the device at version 0.1.
-
Confirm the application versionIn the Android device settings under Apps > ADP AGENCY Immobiliare, look at the Version or Version Name field. The affected version is specifically 0.1.Affected if The installed version is exactly 0.1.
-
Analyze SSL/TLS certificate handlingUse a man-in-the-middle proxy tool (such as Burp Suite or OWASP ZAP) to intercept traffic from the app. Attempt to present a self-signed or forged certificate to the app during an HTTPS request.Affected if The app accepts the forged certificate without error and completes the HTTPS connection, indicating certificate validation is not being performed.
-
Inspect network traffic for plaintext transmissionCapture network traffic while using the app to see if sensitive data is transmitted. Use a network sniffer or proxy to observe whether the app properly validates server certificates during HTTPS connections.Affected if The app transmits sensitive data without proper certificate chain validation, allowing interception.
A user is affected if the Adp4u Adp Agency Immobiliare app version 0.1 is installed and the app accepts invalid or forged X.509 certificates during HTTPS connections, allowing man-in-the-middle attacks.
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 certificate validation in the Android app, including chain-of-trust verification, hostname validation, and consideration of certificate pinning for high-security endpoints.
- Consultation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5843 — 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-5843 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