dbcve.org
Manageengine Firewall AnalyzerApplication · Zohocorp

CVE-2019-11677

CRITICAL · 9.8 CVSS v3.0 Published 2019-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The Custom Report import function in Zoho ManageEngine Firewall Analyzer before 12.3 Build 123224 is vulnerable to XML External Entity (XXE) Injection.

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 · high confidence

The Custom Report import function in Zoho ManageEngine Firewall Analyzer before version 12.3 Build 123224 accepts XML input without disabling external entity processing, allowing authenticated attackers to inject malicious XML that can read local files, perform SSRF attacks, or cause denial of service.

MitigationUpgrade to Zoho ManageEngine Firewall Analyzer version 12.3 Build 123224 or later. Until patched, disable XML external entity processing in the XML parser configuration and restrict import functionality to trusted users only.

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 Firewall AnalyzerApplication
Affected:= 7.2= 7.4= 7.6= 8.0= 8.1= 8.3= 8.5= 12.0= 12.2= 12.3

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

CVSS:3.0/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 checks

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

  1. Identify the installed version of ManageEngine Firewall Analyzer
    Navigate to the product's About or Help section, or check the installation directory for version files. The version is typically displayed in the web UI footer or in the 'version.txt' file in the product root directory.
    Affected if The version displayed is 7.2, 7.4, 7.6, 8.0, 8.1, 8.3, 8.5, 12.0, 12.2, or 12.3 (any build before 123224).
  2. Identify the build number of the installation
    Check the build number in the product's About page or in the 'build.txt' or 'version.properties' file located in the product's installation directory.
    Affected if The build number is lower than 123224 (for example, 12300, 12200, etc.).
  3. Verify if the Custom Report import feature is accessible
    Log into the Firewall Analyzer web interface and navigate to the Reports section to locate the Custom Report import function. This is typically found under Reports > Custom Reports or a similar menu path.
    Affected if The Custom Report import feature is present and accessible to the logged-in user account.
  4. Confirm XML file upload capability
    Attempt to access or observe the file upload interface for importing custom reports. Look for an option to upload XML files as part of the import process.
    Affected if The system accepts XML file uploads through the Custom Report import functionality.

You are affected if your ManageEngine Firewall Analyzer version is 7.2 through 12.3 with a build number below 123224 and the Custom Report import feature is accessible to users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Zoho ManageEngine Firewall Analyzer version 12.3 Build 123224 or later. Until patched, disable XML external entity processing in the XML parser configuration and restrict import functionality to trusted users only.

Recommended fix High confidence

ManageEngine Firewall Analyzer 12.3 Build 123224 or later

  1. Download ManageEngine Firewall Analyzer version 12.3 Build 123224 or later from the official vendor website
  2. Ensure you have a complete backup of your current configuration and database
  3. Stop the Firewall Analyzer service before upgrading
  4. Run the installer/upgrade executable for version 12.3 Build 123224
  5. Follow the on-screen upgrade wizard instructions
  6. Once installation completes, start the Firewall Analyzer service
  7. Verify the upgrade was successful by checking the build number in the About section
  8. Test the Custom Report import function to confirm XXE vulnerability is remediated
Caveat Review release notes for any configuration or feature changes between your current version and 12.3; test custom reports in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Manageengine Firewall Analyzer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11677 — 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-11677 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