# CVE-2023-6253: Saved Uninstall Key in Digital Guardian Agent Uninstaller

> Local attackers can extract a saved uninstall key from memory to bypass security controls and remove the Digital Guardian Agent software.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-2w4h-75hc-2jv2

## What is CVE-2023-6253?

CVE-2023-6253 is a medium-severity vulnerability in Fortra Digital Guardian Agent, published on 22 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A saved encryption key in the Uninstaller in Digital Guardian's Agent before version 7.9.4 allows a local attacker to retrieve the uninstall key and remove the software by extracting the uninstaller key from the memory of the uninstaller file.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2023-6253?

It affects 1 product.


Products: Fortra Digital Guardian Agent.

## How do I fix CVE-2023-6253?

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

## Is CVE-2023-6253 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6253 and fix it if it is affected.

What it is: CVE-2023-6253 is a medium-severity vulnerability in Fortra Digital Guardian Agent, published on 22 Nov 2023. 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-2023-6253 in the wild and no public exploit code.

Affected product: Fortra Digital Guardian Agent. 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-2023-6253/ (Markdown: https://insights.sbomify.com/CVE-2023-6253/index.md)
```

## Sources

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

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