# CVE-2005-0353: Memory corruption in n/a

> Remote attackers can execute arbitrary code by sending large data to UDP port 5093 in Sentinel License Manager.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 8 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-68cv-c3w6-xwxm

## What is CVE-2005-0353?

CVE-2005-0353 is a critical memory corruption vulnerability in n/a, published on 8 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the Sentinel LM (Lservnt) service in the Sentinel License Manager 7.2.0.2 allows remote attackers to execute arbitrary code by sending a large amount of data to UDP port 5093.

## Which versions are affected by CVE-2005-0353?

It affects 1 product.


Products: Safenet Sentinel License Manager.

## How do I fix CVE-2005-0353?

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

## Is CVE-2005-0353 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0353 exists.

Public exploit code:

- SentinelLM UDP Buffer Overflow (metasploit)
- Sentinel LM 7.x - UDP License Service Remote Buffer Overflow (exploitdb)
- Sentinel LM - UDP Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0353 and fix it if it is affected.

What it is: CVE-2005-0353 is a critical memory corruption vulnerability in n/a, published on 8 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0353 exists.

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-2005-0353/ (Markdown: https://insights.sbomify.com/CVE-2005-0353/index.md)
```

## Sources

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

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