# CVE-2013-0707: Code injection in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted file in JustSystems Ichitaro or Hanako 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:** 1 Mar 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2w2v-rc5g-p6fr

## What is CVE-2013-0707?

CVE-2013-0707 is a critical code injection vulnerability in n/a, published on 1 Mar 2013. 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

Unspecified vulnerability in JustSystems Ichitaro 2006 and 2007, Ichitaro Government 2006 and 2007, Ichitaro Portable with oreplug, Hanako 2006 through 2013, Hanako Police, Hanako Police 3, and Hanako Police 2010 allows remote attackers to execute arbitrary code via a crafted file.

## Which versions are affected by CVE-2013-0707?

It affects 5 products.


Products: Justsystems Hanako, Justsystems Hanako Police, Justsystems Hanako Police3, Justsystems Ichitaro, Justsystems Ichitaro Portable.

## How do I fix CVE-2013-0707?

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

## Is CVE-2013-0707 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-2154](https://insights.sbomify.com/CVE-2017-2154/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0707 and fix it if it is affected.

What it is: CVE-2013-0707 is a critical code injection vulnerability in n/a, published on 1 Mar 2013. 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-2013-0707 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-2013-0707/ (Markdown: https://insights.sbomify.com/CVE-2013-0707/index.md)
```

## Sources

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

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