# CVE-2024-25103: Dynamic Link Library (DLL) Hijacking Vulnerability in CDAC AppSamvid Software

> Local attackers with administrative privileges can execute arbitrary code via DLL hijacking in CDAC AppSamvid software.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/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:** 6 Mar 2024
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-f8xf-hh25-83g3

## What is CVE-2024-25103?

CVE-2024-25103 is a medium-severity vulnerability in CDAC AppSamvid Software, published on 6 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability exists in AppSamvid software due to the usage of vulnerable and outdated components. An attacker with local administrative privileges could exploit this by placing malicious DLLs on the targeted system.

Successful exploitation of this vulnerability could allow the attacker to execute arbitrary code on the targeted system.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2024-25103?


## How do I fix CVE-2024-25103?

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

## Is CVE-2024-25103 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25103 and fix it if it is affected.

What it is: CVE-2024-25103 is a medium-severity vulnerability in CDAC AppSamvid Software, published on 6 Mar 2024. 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-2024-25103 in the wild and no public exploit code.

Affected product: CDAC AppSamvid Software. 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-2024-25103/ (Markdown: https://insights.sbomify.com/CVE-2024-25103/index.md)
```

## Sources

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

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