CVE-2011-4770
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 · uneditedThe QIWI Wallet (ru.mw) application before 1.14.2 for Android does not properly protect data, which allows remote attackers to read or modify financial information via a crafted application.
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 · moderate confidenceThe QIWI Wallet Android application before version 1.14.2 fails to properly protect sensitive financial data stored on the device. A malicious application installed on the same device can exploit this inadequate data protection to read or modify financial information processed by the wallet app.
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<= 1.14.2= 1.13CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Qiwi Wallet app is installedOpen Android Settings > Apps > Applications Manager, or check your app drawer for the Qiwi Wallet application icon. Alternatively, run: adb shell pm list packages | grep qiwiAffected if The Qiwi Wallet application is present on the device
-
Check installed version numberNavigate to Settings > Apps > Qiwi Wallet > Version information, or use: adb shell dumpsys package com.qiwi.wallet | grep versionNameAffected if Version displayed is 1.14.2 or lower, or specifically shows version 1.13
-
Determine if financial data exists locallyCheck if the app has been used to conduct transactions or store payment methods. Inspect app data directory at /data/data/com.qiwi.wallet/ or check if saved cards or transaction history are visible within the appAffected if Sensitive financial information such as saved payment cards, transaction history, or account balance data is stored locally on the device
-
Verify unknown sources installation settingGo to Settings > Security > Unknown sources (or Settings > Apps > Install unknown apps) and check if installation from unknown sources is enabledAffected if Unknown sources is enabled, allowing installation of malicious apps that could exploit the vulnerability
You are affected if Qiwi Wallet version 1.14.2 or lower (especially 1.13) is installed AND sensitive financial data exists on the device, particularly if unknown sources are enabled allowing potential malicious app installation.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the QIWI Wallet application to version 1.14.2 or later, which contains proper data protection mechanisms. Organizations should also implement additional mobile device security controls and advise users to only install applications from trusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-4770 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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