dbcve.org
Virtual Wallet By PncApplication · Pnc

CVE-2014-6881

MEDIUM · 5.4 CVSS v2.0 Published 2014-10-02
Fix available
A fix is available. Upgrade to after 2.1.1 or later.
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 PNC Virtual Wallet (aka com.pnc.ecommerce.mobile.vw.android) application before 2.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 PNC Virtual Wallet Android application before version 2.2 fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept sensitive financial data by presenting forged certificates. This is a classic SSL certificate validation bypass vulnerability in the mobile app's network layer.

MitigationUpdate the PNC Virtual Wallet Android application to version 2.2 or later, which implements proper X.509 certificate validation. For organizations, ensure mobile banking applications are kept current and consider implementing network-level SSL/TLS inspection as an additional security layer.

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
Virtual Wallet By PncApplication
Affected:<= 2.1.1

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. Locate PNC Virtual Wallet app on Android device
    Open device Settings > Apps > Apps Manager (or Apps & notifications) and search for 'Virtual Wallet' or 'PNC' to find the installed application
    Affected if The app is present on the device
  2. Identify installed app version
    In the app info screen, locate the 'Version' or 'Version number' field displayed under the app name
    Affected if A version number is displayed (indicating the app is installed)
  3. Compare version against vulnerable range
    Note the version number and compare it to the affected range: versions 2.1.1 and earlier are vulnerable. The fix version is 2.2
    Affected if Installed version is 2.1.1 or lower (e.g., 2.1.1, 2.1.0, 2.0.x, etc.)

You are affected if PNC Virtual Wallet Android app version 2.1.1 or any earlier version is installed on your device.

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.1.1
Interim mitigation

Update the PNC Virtual Wallet Android application to version 2.2 or later, which implements proper X.509 certificate validation. For organizations, ensure mobile banking applications are kept current and consider implementing network-level SSL/TLS inspection as an additional security layer.

Fix this in Virtual Wallet By Pnc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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