dbcve.org
Denny\'sApplication · 7andi Fs.co

CVE-2014-1967

MEDIUM · 5.8 CVSS v2.0 Published 2014-02-27
Fix available
A fix is available. Upgrade to after 2.0.0 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable 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 Denny's application before 2.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 confidence

The Denny's Android application before version 2.0.1 fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting forged certificates.

MitigationUpdate the Denny's Android application to version 2.0.1 or later which implements proper SSL certificate validation. Ensure all network communications validate server certificates before trusting the connection.

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
Denny\'sApplication
Affected:<= 2.0.0= 1.0.1= 1.0.2

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
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/A:N

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 Denny's Android app is installed
    Check device for Denny's app - look for app named 'Denny's' or 'Dennys' in installed applications list. On Android, use 'adb shell pm list packages' or check Settings > Apps.
    Affected if The Denny's app is present on the device
  2. Determine installed app version
    Check the app version in Google Play Store (app details page), in the app's Settings/About section, or by examining the APK file using 'aapt dump badging dennys.apk' to read the versionName and versionCode.
    Affected if Version cannot be determined or is listed as 1.0.1, 1.0.2, or any version up to and including 2.0.0
  3. Compare version against affected ranges
    Compare the installed version number to the affected versions: 1.0.1, 1.0.2, and all versions <= 2.0.0. Version 2.0.1 and later are NOT affected.
    Affected if Installed version is 1.0.1, 1.0.2, or any version from 1.0.0 through 2.0.0

If the Denny's Android application version is 1.0.1, 1.0.2, or any version from 1.0.0 to 2.0.0, the device is vulnerable to MITM attacks due to missing SSL certificate validation.

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
Upgrade available Upgrade to a release after 2.0.0
Interim mitigation

Update the Denny's Android application to version 2.0.1 or later which implements proper SSL certificate validation. Ensure all network communications validate server certificates before trusting the connection.

Fix this in Denny\'s Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1967 — 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-1967 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