dbcve.org
AnaApplication

CVE-2018-0611

HIGH · 7.4 CVSS v3.0 Published 2018-06-26
Fix available
A fix is available. Upgrade to after 4.0.22 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 ANA App for iOS version 4.0.22 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 ANA App for iOS versions 4.0.22 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 fraudulent certificates.

MitigationUpdate the ANA App to version 4.0.23 or later which implements proper SSL certificate validation. Avoid using the app on untrusted networks until updated.

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
AnaApplication
Affected:<= 4.0.22

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. Verify ANA App is installed
    On the iOS device, navigate to Settings > General > iPhone Storage (or iPad Storage) and look for the ANA App in the list of installed applications.
    Affected if The ANA App is present on the device
  2. Identify installed version
    In Settings > General > iPhone Storage (or iPad Storage), tap on the ANA App to view its version information, or check the version shown in the App Store app under the app listing.
    Affected if Unable to determine the version number
  3. Compare version to affected range
    Compare the installed version number to the affected range. The app version is typically displayed as a three-part number (e.g., 4.0.22).
    Affected if The installed version is 4.0.22 or earlier (e.g., 4.0.20, 4.0.15, etc.)
  4. Assess network usage context
    Consider whether the ANA App is used on untrusted or public networks (e.g., WiFi hotspots, shared networks) where a man-in-the-middle attack could be performed.
    Affected if The app is used on untrusted networks and the version is 4.0.22 or earlier

You are affected if the ANA App for iOS is installed at version 4.0.22 or earlier and is used on networks where an attacker could intercept traffic.

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

Update the ANA App to version 4.0.23 or later which implements proper SSL certificate validation. Avoid using the app on untrusted networks until updated.

Fix this in Ana 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 the upgrade done

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-2018-0611 — 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-0611 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