# CVE-2024-4894: ITPison OMICARD EDM - Server-Side Request Forgery

> Unauthenticated attackers can exploit SSRF in ITPison OMICARD EDM to probe internal network information via unfiltered URL parameters.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-5jj7-gjcq-hrc8

## What is CVE-2024-4894?

CVE-2024-4894 is a medium-severity server-side request forgery vulnerability in ITPison OMICARD EDM, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ITPison OMICARD EDM  fails to properly filter specific URL parameter, allowing unauthenticated remote attackers to modify the parameters and conduct Server-Side Request Forgery (SSRF) attacks. This vulnerability enables attackers to probe internal network information.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2024-4894 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4894 is a medium-severity server-side request forgery vulnerability in ITPison OMICARD EDM, published on 15 May 2024. 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-2024-4894 in the wild and no public exploit code.

Affected product: ITPison OMICARD EDM. 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-4894/ (Markdown: https://insights.sbomify.com/CVE-2024-4894/index.md)
```

## Sources

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

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