CVE-2020-24743
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was found in /showReports.do Zoho ManageEngine Applications Manager up to 14550, allows attackers to gain escalated privileges via the resourceid parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceZoho ManageEngine Applications Manager versions up to 14550 contain a privilege escalation vulnerability in the /showReports.do endpoint. The resourceid parameter is not properly validated or authorized, allowing authenticated attackers to manipulate this parameter to access reports and resources outside their assigned permissions, effectively escalating privileges to higher-privileged users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 14.5= 14.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Applications Manager versionLocate the installed version of Zoho ManageEngine Applications Manager. This is typically visible in the product UI header, about page, or in the installation directory version file. Compare against the affected version range (versions up to and including 14.5 / build 14550).Affected if Installed version is 14.5 or lower (build 14550 or below)
-
Confirm /showReports.do endpoint existsVerify that the /showReports.do web endpoint is present and accessible in the Applications Manager installation. This is typically found at http(s)://[hostname]:[port]/showReports.do.Affected if The endpoint exists and responds to requests in the affected version range
-
Verify authenticated user accessLog into Applications Manager with a standard user account that has limited permissions. Confirm the user role assigned and the scope of reports/resources they are authorized to access.Affected if User authentication is functional and role-based access controls are in use
-
Test resourceid parameter manipulationUsing an authenticated low-privilege session, make a request to /showReports.do with a resourceid parameter value referencing a resource (such as a report or data) that the current user should NOT have permission to view. Observe whether the server returns the unauthorized resource.Affected if The server returns data for resourceid values outside the user's assigned permissions, indicating broken access control
-
Check authorization headers in responsesExamine HTTP responses when requesting /showReports.do with different resourceid values. Look for signs that authorization checks are not being enforced, such as successful 200 responses for cross-privilege-level resources.Affected if Responses indicate unauthorized resources are accessible without proper authorization validation
The environment is affected if Applications Manager version is 14.5 or lower and the /showReports.do endpoint permits authenticated users to access resources outside their assigned permission scope via manipulation of the resourceid parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped14.5
Implement proper authorization checks on the resourceid parameter in /showReports.do to ensure users can only access resources they are explicitly permitted to view, and validate all user-supplied resource identifiers against the authenticated user's permission set.
Applications Manager version 14.6 or later
- 1. Backup the current Applications Manager installation and database before proceeding with any upgrade.
- 2. Download the latest version of ManageEngine Applications Manager from the official ManageEngine downloads page (www.manageengine.com).
- 3. Stop the Applications Manager service.
- 4. Install/upgrade to version 14.6 or later (the fixed release that addresses the privilege escalation vulnerability in /showReports.do).
- 5. Start the Applications Manager service.
- 6. Verify the upgrade was successful by logging into the admin console.
- 7. Confirm the resourceid parameter vulnerability is no longer exploitable by testing the /showReports.do endpoint with a non-privileged account.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24743 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-24743 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data