# CVE-2012-0269: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted image file in JustSystems office applications.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Apr 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7x99-5fhm-jf5v

## What is CVE-2012-0269?

CVE-2012-0269 is a critical memory corruption vulnerability in n/a, published on 27 Apr 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in JustSystems Ichitaro 2011 Sou, Ichitaro 2006 through 2011, Ichitaro Government 2006 through 2010, Ichitaro Portable with oreplug, Ichitaro Viewer, JUST School, JUST School 2009 and 2010, JUST Jump 4, JUST Frontier, oreplug, Shuriken Pro4, Shuriken 2007 through 2010, Shuriken Pro4 Corporate Edition, Shuriken CE/2007 through CE/2009 Corporate Edition, Shuriken 2010 Corporate Edition, Rekishimail Sengokubusho no missho, and Bakumatsushishi no missho allows remote attackers to execute arbitrary code via a crafted image file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2012-0269?

It affects 11 products.


Products: Justsystems Ichitaro, Justsystems Ichitaro Portable With Oreplug, Justsystems Ichitaro Viewer, Justsystems Just Frontier, Justsystems Just Jump, Justsystems Just School, Justsystems Oreplug, Justsystems Rekishimail Bakumatsushishi No Missho, Justsystems Rekishimail Sengokubusho No Missho, Justsystems Shuriken, Justsystems Shuriken Pro.

## How do I fix CVE-2012-0269?

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

## Is CVE-2012-0269 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-7247](https://insights.sbomify.com/CVE-2014-7247/): Other in n/a (critical 10.0)
- [CVE-2013-3644](https://insights.sbomify.com/CVE-2013-3644/): Code injection in n/a (critical 10.0)
- [CVE-2013-5990](https://insights.sbomify.com/CVE-2013-5990/): Code injection in n/a (critical 9.3)
- [CVE-2011-1331](https://insights.sbomify.com/CVE-2011-1331/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-3915](https://insights.sbomify.com/CVE-2010-3915/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0269 and fix it if it is affected.

What it is: CVE-2012-0269 is a critical memory corruption vulnerability in n/a, published on 27 Apr 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-0269 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-2012-0269/ (Markdown: https://insights.sbomify.com/CVE-2012-0269/index.md)
```

## Sources

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

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