CVE-2011-4771
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 Scan to PDF Free (com.scan.to.pdf.trial) application 2.0.4 for Android does not properly protect data, which allows remote attackers to read or modify scanned files and a Google account 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 Scan to PDF Free Android application 2.0.4 fails to properly protect its data, allowing a malicious application installed on the same device to read and modify scanned files stored by the app, as well as access the associated Google account credentials. This is a classic insecure data storage vulnerability where sensitive data is stored without adequate protection.
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= 2.0.4CVSS 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 the application is installedCheck the Android device for Lucion Scan To Pdf Free (also known as Scan to PDF Free) in the installed applications listAffected if The app is present on the device
-
Confirm the installed versionView the app details in Settings > Applications > Scan To Pdf Free and check the version numberAffected if Version is exactly 2.0.4
-
Check app data storage permissionsUse a file explorer or ADB shell to inspect the permissions on the app's private data directory (typically /data/data/com.lucion.scan2pdffree/)Affected if Files or directories within the app's data folder are world-readable (permissions show 'other' has read access, such as 'rwxrwxrwx' or 'drwxrwxrwx')
-
Verify scanned files accessibilityCheck the directory where scanned PDFs are stored (commonly in the app's files or documents folder) and attempt to list/read files from another non-privileged app or via ADB without rootAffected if Scanned PDF files can be accessed by other applications or are stored in a world-readable location
-
Check for credential exposureInspect shared preferences or database files within the app's data directory for stored Google account credentialsAffected if Credentials or authentication tokens are stored in plaintext files with permissive permissions (world-readable)
A user is affected if Lucion Scan To Pdf Free version 2.0.4 is installed and its data storage locations are world-readable, allowing other apps to access scanned files and stored credentials without special permissions.
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 to the latest version of the application if available, or replace with an alternative scanning application that properly encrypts stored data and secures credential handling. For enterprise environments, enforce policies restricting installation of unvetted applications on devices handling sensitive data.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4771 — 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-4771 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