# CVE-2011-4771: Missing authorization in n/a

> A malicious app can read or modify scanned files and Google account data in Scan to PDF Free due to improper data protection.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jan 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-46gp-59r3-724f

## What is CVE-2011-4771?

CVE-2011-4771 is a medium-severity missing authorization vulnerability in n/a, published on 25 Jan 2012. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The 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.

Weakness: CWE-264

## Which versions are affected by CVE-2011-4771?

It affects 1 product.


Products: Lucion Scan to Pdf Free.

## How do I fix CVE-2011-4771?

No fix has been published for CVE-2011-4771 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-4771 being exploited?

There is no known exploitation of CVE-2011-4771 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4771 and fix it if it is affected.

What it is: CVE-2011-4771 is a medium-severity missing authorization vulnerability in n/a, published on 25 Jan 2012. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-4771 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-4771/ (Markdown: https://insights.sbomify.com/CVE-2011-4771/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-4771
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-4771
- OSV: https://osv.dev/vulnerability/CVE-2011-4771

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-4771/
Summaries are generated and may contain mistakes; the official description above is the record.