dbcve.org
Harpers Bazaar ArtApplication · Itp

CVE-2014-7795

MEDIUM · 5.4 CVSS v2.0 Published 2014-10-21
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 Harpers Bazaar Art (aka com.itp.harpersart) application @7F080181 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 Harpers Bazaar Art Android application fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept communications by presenting fraudulent certificates. This enables attackers to spoof legitimate servers and capture sensitive data transmitted between the app and backend services.

MitigationImplement proper SSL certificate validation by using Android's default TrustManager or certificate pinning to verify server certificates before establishing encrypted connections.

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
Harpers Bazaar ArtApplication
Affected:= \@7f080181

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 the Harpers Bazaar Art app is installed
    On the Android device, go to Settings > Apps > All Apps and search for 'Harpers Bazaar' or 'Harpers Bazaar Art', or use the command 'adb shell pm list packages' to list all installed packages and look for packages containing 'harpers' or 'bazaar'.
    Affected if The Harpers Bazaar Art application is found on the device.
  2. Determine the installed version of the app
    In Settings > Apps > App Info for Harpers Bazaar Art, note the version name and version code. Alternatively, use 'adb shell dumpsys package <package_name>' to get detailed version information including the version code.
    Affected if The version code matches 7f080181 (as indicated by the affected version string \@7f080181) or falls within the specific affected build.
  3. Check if the app accepts invalid SSL certificates
    Use a network proxy tool (such as Burp Suite or OWASP ZAP) to intercept traffic from the app. Configure the proxy with an invalid or self-signed certificate and attempt to use the app's network features. If the app connects successfully without certificate validation errors, the vulnerability is present.
    Affected if The app successfully connects to backend servers when presented with invalid, expired, or self-signed SSL certificates, indicating certificate validation is not enforced.
  4. Inspect the app's network security configuration
    If you have access to the APK file, decompile it and examine the AndroidManifest.xml for any network-related permissions, then check the smali or Java code for custom TrustManager implementations or hostname verifier configurations that may bypass SSL validation.
    Affected if The app code contains custom TrustManager implementations that override default certificate validation (for example, trusting all certificates) or disables hostname verification.

A user is affected if the Harpers Bazaar Art Android app version 7f080181 is installed and the app successfully establishes SSL connections with invalid or untrusted certificates.

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 by using Android's default TrustManager or certificate pinning to verify server certificates before establishing encrypted connections.

Fix this in Harpers Bazaar Art Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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