dbcve.org
Manageengine AssetexplorerApplication · Zohocorp

CVE-2019-12994

CRITICAL · 9.1 CVSS v3.0 Published 2019-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Server Side Request Forgery (SSRF) exists in Zoho ManageEngine AssetExplorer version 6.2.0 for the AJaxServlet servlet via a parameter in a URL.

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 confidence

A Server Side Request Forgery (SSRF) vulnerability exists in Zoho ManageEngine AssetExplorer version 6.2.0 within the AJaxServlet component. Attackers can exploit this by supplying a malicious URL parameter, causing the server to make arbitrary requests to internal or external resources, potentially exposing sensitive internal services.

MitigationApply the vendor patch for CVE-2019-12994; if unavailable, restrict the application's network access and implement strict URL validation with allowlists to prevent arbitrary request forwarding.

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
Manageengine AssetexplorerApplication
Affected:= 6.2.0

CVSS 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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify AssetExplorer installation and version
    Locate the ManageEngine AssetExplorer installation directory and check for version information in the product's about page, version file, or build number. Common paths include /opt/ManageEngine/AssetExplorer or C:\ManageEngine\AssetExplorer. Look for a version.txt, build.info, or the application's built-in version display accessible via the web interface at /assetExplorer/api/index.jsp or the About link in the UI.
    Affected if The installed version is exactly 6.2.0 or the build number matches version 6.2.0
  2. Confirm the AJaxServlet component is accessible
    Verify that the AJaxServlet endpoint is available by checking if the web interface is running and accessible. The vulnerability exists in the AJaxServlet component, typically accessed via URL patterns containing 'AjaxServlet' or 'ajax' in the application's web routing. Attempt a request to common AJAX endpoints or check the application's exposed web services.
    Affected if The web interface and AJaxServlet endpoint are externally or internally accessible without proper authentication controls
  3. Assess network exposure of the AssetExplorer service
    Determine if the AssetExplorer web service is listening on external network interfaces (0.0.0.0) rather than localhost only. Check the server's listening ports using 'netstat -an' or 'ss -tlnp' and identify if port 8080 or the configured AssetExplorer port is bound to non-local addresses. Review firewall rules and network segmentation configurations.
    Affected if The AssetExplorer web interface is reachable from untrusted networks or the application server has broad network access that could facilitate SSRF-based attacks on internal resources

You are affected if ManageEngine AssetExplorer version 6.2.0 is installed and the web-based AJaxServlet component is accessible to users or attackers who can submit crafted URL parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CVE-2019-12994; if unavailable, restrict the application's network access and implement strict URL validation with allowlists to prevent arbitrary request forwarding.

Fix this in Manageengine Assetexplorer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-12994 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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