# CVE-2009-4738: Auth bypass in n/a

> Physically proximate attackers can bypass the screen lock and execute arbitrary commands with system privileges in ATOK software.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 18 Jan 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6hqf-fwf2-vf87

## What is CVE-2009-4738?

CVE-2009-4738 is a high-severity authentication bypass vulnerability in n/a, published on 18 Jan 2013. 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

Unspecified vulnerability in JustSystems Corporation ATOK 2006 through 2009 and ATOK flat-rate service, and Just Smile 4 with the ATOK Smile module, allows physically proximate users to bypass the screen lock and execute commands with system privileges via unknown vectors related to "launching external applications."

## Which versions are affected by CVE-2009-4738?

It affects 3 products.


Products: Justsystems Atok, Justsystems Atok Flat-Rate Service, Justsystems Just Smile.

## How do I fix CVE-2009-4738?

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

## Is CVE-2009-4738 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4016](https://insights.sbomify.com/CVE-2012-4016/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4738 and fix it if it is affected.

What it is: CVE-2009-4738 is a high-severity authentication bypass vulnerability in n/a, published on 18 Jan 2013. 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-2009-4738 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-2009-4738/ (Markdown: https://insights.sbomify.com/CVE-2009-4738/index.md)
```

## Sources

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

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