LiveActive security incident?Get immediate response
CVE Record

CVE-2011-1136: In tesseract 2.03 and 2.04, an attacker can rewrite an arbitrary user file by guessing the PID and creating...

In tesseract 2.03 and 2.04, an attacker can rewrite an arbitrary user file by guessing the PID and creating a link to the user's file.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2011-1136 is an old Tesseract OCR issue affecting versions 2.03 and 2.04. A local attacker who can influence temporary link creation may overwrite a file owned by the user running Tesseract. Business risk is mainly legacy-system integrity loss, not internet-scale compromise based on the supplied sources.

Executive priority

Treat this as a legacy hygiene issue with moderate priority. It warrants remediation if old Tesseract versions remain in production, especially on shared systems, but supplied evidence does not indicate active exploitation or broad remote exposure.

Technical view

The described flaw allows arbitrary user-file rewrite by guessing the process ID and creating a link to the target user's file. The sources identify Tesseract 2.03 and 2.04, but provide no CVSS, CWE, confirmed fixed version, or remote attack path in the supplied bundle.

Likely exposure

Exposure is most likely on legacy systems still running Tesseract 2.03 or 2.04, especially shared hosts or OCR pipelines processing untrusted jobs. The supplied sources do not support broader product or version claims.

Exploitation context

CISA KEV is false, and the supplied sources do not report active exploitation. The described attack appears to require local filesystem interaction and process-ID guessing; remote exploitation is not supported by the provided evidence.

Researcher notes

The source bundle is sparse: no CVSS, CWE, patch statement, or detailed advisory text is provided. Analysis should stay limited to Tesseract 2.03 and 2.04 and the file-rewrite behavior described in the CVE summary and distro references.

Mitigation direction

  • Inventory systems for Tesseract 2.03 and 2.04.
  • Check Debian, Ubuntu, or vendor package guidance for corrected builds.
  • Avoid running legacy Tesseract jobs as privileged users.
  • Limit untrusted local access on systems running vulnerable OCR workflows.
  • Isolate OCR processing until vendor remediation is confirmed.

Validation and detection

  • Confirm installed Tesseract versions across hosts and containers.
  • Identify OCR jobs running on shared or multi-user systems.
  • Review whether vulnerable versions process untrusted input.
  • Check vendor package history for CVE-2011-1136 remediation status.
  • Document any remaining legacy exception and compensating controls.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2011-1136 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.