# CVE-2007-2883: Information disclosure in n/a

> Local attackers can read plaintext credentials from memory or paging files, bypassing security protections on stolen devices.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c67p-2c36-mvjf

## What is CVE-2007-2883?

CVE-2007-2883 is a medium-severity vulnerability in n/a, published on 30 May 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Credant Mobile Guardian Shield for Windows 5.2.1.105 and earlier stores account names and passwords in plaintext in memory, which allows local users to obtain sensitive information by (1) reading the paging file or (2) dumping and searching the memory image.  NOTE: This issue crosses privilege boundaries because the product is intended to protect the data on a stolen computer.

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

It affects 1 product.


Products: Credant Credant Mobile Guardian Shield - Windows.

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

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

## Is CVE-2007-2883 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2883 is a medium-severity vulnerability in n/a, published on 30 May 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2883 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-2883/ (Markdown: https://insights.sbomify.com/CVE-2007-2883/index.md)
```

## Sources

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

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