# CVE-2019-12994: Server-side request forgery in n/a

> An attacker can exploit a Server Side Request Forgery vulnerability in Zoho ManageEngine AssetExplorer to access internal resources via the AJaxServlet.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c3rp-7vxj-5h98

## What is CVE-2019-12994?

CVE-2019-12994 is a critical server-side request forgery vulnerability in n/a, published on 8 Aug 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Server Side Request Forgery (SSRF) exists in Zoho ManageEngine AssetExplorer version 6.2.0 for the AJaxServlet servlet via a parameter in a URL.

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

## Which versions are affected by CVE-2019-12994?

It affects 1 product.


Products: Zohocorp Manageengine Assetexplorer.

## How do I fix CVE-2019-12994?

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

## Is CVE-2019-12994 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-20110](https://insights.sbomify.com/CVE-2021-20110/): Integer overflow in Manage Engine Asset Explorer Agent (critical 9.8)
- [CVE-2019-12959](https://insights.sbomify.com/CVE-2019-12959/): Server-side request forgery in n/a (high 8.8)
- [CVE-2019-14693](https://insights.sbomify.com/CVE-2019-14693/): XML external entity in n/a (high 8.5)
- [CVE-2023-26601](https://insights.sbomify.com/CVE-2023-26601/): Denial of service in n/a (high 7.5)
- [CVE-2022-35403](https://insights.sbomify.com/CVE-2022-35403/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12994 and fix it if it is affected.

What it is: CVE-2019-12994 is a critical server-side request forgery vulnerability in n/a, published on 8 Aug 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12994 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-2019-12994/ (Markdown: https://insights.sbomify.com/CVE-2019-12994/index.md)
```

## Sources

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

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