# CVE-2007-4785: Security feature bypass in n/a

> Remote attackers can bypass malware detection by placing files in a hidden directory created by Sony Micro Vault fingerprint software.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v5rr-4m5q-q852

## What is CVE-2007-4785?

CVE-2007-4785 is a medium-severity vulnerability in n/a, published on 10 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sony Micro Vault Fingerprint Access Software, as distributed with Sony Micro Vault USM-F USB flash drives, installs a driver that hides a directory under %WINDIR%, which might allow remote attackers to bypass malware detection by placing files in this directory.

## Which versions are affected by CVE-2007-4785?

It affects 1 product.


Products: Sony Micro Vault Fingerprint Access Software.

## How do I fix CVE-2007-4785?

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

## Is CVE-2007-4785 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4785 and fix it if it is affected.

What it is: CVE-2007-4785 is a medium-severity vulnerability in n/a, published on 10 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4785 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-2007-4785/ (Markdown: https://insights.sbomify.com/CVE-2007-4785/index.md)
```

## Sources

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

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