How severe is CVE-2010-4338?

No CVSS score has been assigned to CVE-2010-4338 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-4338?

CVE-2010-4338 affects the following packages: ocrodjvu (Debian:10). Ecosystems affected: Debian:10.

How do I fix CVE-2010-4338?

Update ocrodjvu to 0.4.6-2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-4338 is resolved across your whole dependency graph.

How do I detect CVE-2010-4338 in my Debian:10 dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ocrodjvu. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2010-4338 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2010-4338?

O3 pinpoints whether CVE-2010-4338 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2010-4338 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-4338 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2010-4338?

CVE-2010-4338 is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2010-4338 published, and has it been updated?

CVE-2010-4338 was published on January 20, 2011 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

📦 Debian:10

CVE-2010-4338

CVE-2010-4338 is a CWE-59 vulnerability in ocrodjvu. O3 Security confirms whether CVE-2010-4338 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

ocrodjvu is vulnerable to Arbitrary File Modification via symlink attack

Also known asGHSA-5pjj-7m4p-wfh2PYSEC-2026-886

Published

Jan 20, 2011

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

📦ocrodjvu

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Debian:10 packages — download data is not available via public APIs for these ecosystems.

Description

ocrodjvu 0.4.6-1 on Debian GNU/Linux allows local users to modify arbitrary files via a symlink attack on temporary files that are generated when Cuneiform is invoked as the OCR engine.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Debian:10	`ocrodjvu`	all versions	0.4.6-2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ocrodjvu. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ocrodjvu to 0.4.6-2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-4338 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2010-4338 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2010-4338. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

ocrodjvu 0.4.6-1 on Debian GNU/Linux allows local users to modify arbitrary files via a symlink attack on temporary files that are generated when Cuneiform is invoked as the OCR engine.

O3 Security · Impact-Aware SCA

Is CVE-2010-4338 in your dependencies?

O3 detects CVE-2010-4338 across Debian:10 dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works