# CVE-2021-20110: Integer overflow in Manage Engine Asset Explorer Agent

> An integer overflow in the Manage Engine Asset Explorer Agent allows remote attackers to execute arbitrary code with SYSTEM privileges via a crafted HTTP response.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jj4p-9287-5h8h, UBUNTU-CVE-2021-20110

## What is CVE-2021-20110?

CVE-2021-20110 is a critical vulnerability in Manage Engine Asset Explorer Agent, published on 19 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to Manage Engine Asset Explorer Agent 1.0.34 not validating HTTPS certificates, an attacker on the network can statically configure their IP address to match the Asset Explorer's Server IP address. This will allow an attacker to send a NEWSCAN request to a listening agent on the network as well as receive the agent's HTTP request verifying its authtoken. In httphandler.cpp, the agent reaching out over HTTP is vulnerable to an Integer Overflow, which can be turned into a Heap Overflow allowing for remote code execution as NT AUTHORITY/SYSTEM on the agent machine. The Integer Overflow occurs when receiving POST response from the Manage Engine server, and the agent calling "HttpQueryInfoW" in order to get the "Content-Length" size from the incoming POST request. This size is taken, but multiplied to a larger amount. If an attacker specifies a Content-Length size of 1073741823 or larger, this integer arithmetic will wrap the value back around to smaller integer, then calls "calloc" with this size to allocate memory. The following API "InternetReadFile" will copy the POST data into this buffer, which will be too small for the contents, and cause heap overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2021-20110?

It affects 1 product.


Products: Zohocorp Manageengine Assetexplorer.

## How do I fix CVE-2021-20110?

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

## Is CVE-2021-20110 being exploited?

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

## Other vulnerabilities in Manage Engine Asset Explorer Agent

- [CVE-2019-12994](https://insights.sbomify.com/CVE-2019-12994/): Server-side request forgery in n/a (critical 9.1)
- [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-2021-20110 and fix it if it is affected.

What it is: CVE-2021-20110 is a critical vulnerability in Manage Engine Asset Explorer Agent, published on 19 Jul 2021. 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-2021-20110 in the wild and no public exploit code.

Affected product: Manage Engine Asset Explorer 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-2021-20110/ (Markdown: https://insights.sbomify.com/CVE-2021-20110/index.md)
```

## Sources

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

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