dbcve.org
Auto TraderApplication · Autotrader.co.za

CVE-2014-5997

MEDIUM · 5.4 CVSS v2.0 Published 2014-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
The Auto Trader (aka za.co.autotrader.android.app) application 2 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 confidence

The Auto Trader Android app version 2 fails to validate X.509 certificates from SSL servers during TLS/SSL connections. This allows an attacker on the same network to perform a man-in-the-middle attack, intercepting traffic by presenting a fraudulent certificate and capturing sensitive user data transmitted to the backend.

MitigationImplement proper SSL certificate validation in the Android application, including certificate pinning or full X.509 chain verification using standard Android security APIs (e.g., CertificatePinner or custom TrustManager).

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
Auto TraderApplication
Affected:= 2.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Autotrader app is installed
    On the Android device, go to Settings > Apps >查看已安装的应用，搜索 'Auto Trader' 或 'Autotrader'。或者使用adb命令: adb shell pm list packages | grep -i trader
    Affected if The Autotrader.co.za Auto Trader app is installed on the device
  2. Check the installed version number
    In Settings > Apps > Auto Trader，查看版本信息。或者使用adb命令: adb shell dumpsys package <package_name> | grep versionName。已知受影响的版本为 2.0
    Affected if The app version is exactly 2.0
  3. Verify if the app uses network connections
    检查设备是否连接到网络，然后使用adb命令监控网络活动: adb shell netstat -an | grep <app_pid> 或使用Burp Suite等工具拦截来自该应用的流量
    Affected if The app makes outbound network connections to backend servers

If the Autotrader.co.za Auto Trader app version 2.0 is installed and makes network connections, the SSL certificate validation flaw is present and the traffic could be intercepted via MITM attack.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper SSL certificate validation in the Android application, including certificate pinning or full X.509 chain verification using standard Android security APIs (e.g., CertificatePinner or custom TrustManager).

Fix this in Auto Trader Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-5997 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-5997 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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