dbcve.org
Dhc Online ShopApplication · Dhc

CVE-2018-0622

HIGH · 7.4 CVSS v3.0 Published 2018-07-26
Fix available
A fix is available. Upgrade to after 3.2.0 or later.
See remediation →
83/100
Remediation priority · High
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 DHC Online Shop App for Android version 3.2.0 and earlier 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 DHC Online Shop App for Android versions 3.2.0 and earlier fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to spoof servers and intercept sensitive data by presenting forged certificates.

MitigationUpdate to a patched version of the app that implements proper SSL certificate validation using Android's certificate pinning or custom TrustManager; avoid conducting sensitive transactions over untrusted networks until patched.

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
Dhc Online ShopApplication
Affected:<= 3.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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Check the installed version of DHC Online Shop app
    On the Android device, go to Settings > Apps > DHC Online Shop (or Dhc Dhc Online Shop) and look at the Version field under App Info. Alternatively, use adb shell pm list packages and adb shell dumpsys package <package_name> to retrieve version information.
    Affected if The version displayed is 3.2.0 or any version lower than 3.2.0
  2. Identify the package name of the app
    Run 'adb shell pm list packages | grep -i dhc' or 'adb shell pm list packages | grep -i shop' to find the package name. This is needed for further analysis.
    Affected if A package containing 'dhc' and 'shop' in the name is found on the device
  3. Analyze the app for proper SSL certificate validation
    Decompile the APK using tools like apktool, then examine the smali or Java source code for the presence of a custom TrustManager or certificate pinning implementation. Look for classes that extend TrustManager or use implementations like CertificatePinner. Search for 'TrustManager' and 'ALLOW_ALL_HOSTNAME_VERIFIER' or 'HostnameVerifier' with relaxed settings.
    Affected if The app code does not implement a custom TrustManager or certificate pinning, or uses a TrustManager that accepts all certificates (e.g., TrustAllManager), or disables hostname verification
  4. Check network traffic interception capability
    Attempt to proxy network traffic through a tool like Burp Suite or OWASP ZAP using a self-signed certificate. If the app successfully connects and transmits sensitive data without certificate validation errors, the vulnerability is present.
    Affected if The app successfully communicates through the proxy with a self-signed certificate, indicating no proper certificate validation is occurring
  5. Verify Android network security configuration
    If the APK can be analyzed, check the res/xml/network_security_config.xml file for any configurations that allow cleartext traffic or disable certificate validation. Also check AndroidManifest.xml for any network security configurations.
    Affected if Network security config is missing, allows cleartext traffic to sensitive domains, or contains debuggable trust anchors

You are affected if the installed DHC Online Shop app version is 3.2.0 or lower and the app does not implement proper SSL certificate validation (custom TrustManager or certificate pinning), as demonstrated by accepting self-signed certificates during MITM testing.

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 3.2.0
Interim mitigation

Update to a patched version of the app that implements proper SSL certificate validation using Android's certificate pinning or custom TrustManager; avoid conducting sensitive transactions over untrusted networks until patched.

Fix this in Dhc Online Shop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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