dbcve.org
Manageengine Firewall AnalyzerApplication · Zohocorp

CVE-2019-11678

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 "default reports" feature in Zoho ManageEngine Firewall Analyzer before 12.3 Build 123218 is vulnerable to SQL 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

SQL injection vulnerability in the 'default reports' feature of Zoho ManageEngine Firewall Analyzer allows unauthenticated attackers to execute arbitrary SQL commands by injecting malicious payloads into report parameters, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.

MitigationUpgrade to Zoho ManageEngine Firewall Analyzer version 12.3 Build 123218 or later which contains the patched code to remediate the SQL injection vulnerability in the default reports feature.

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. Verify Zoho ManageEngine Firewall Analyzer is installed
    Check for the application by looking for the installation directory (typically in C:\Program Files\ManageEngine\FirewallAnalyzer on Windows or /opt/ManageEngine/FirewallAnalyzer on Linux), or by accessing the web interface on port 8080 or 8443.
    Affected if The product is installed and running.
  2. Identify the installed version
    Access the web interface and navigate to the 'About' or 'Support' page, or check the version.txt or version.info file in the installation directory.
    Affected if The installed version matches 7.2, 7.4, 7.6, 8.0, 8.1, 8.3, 8.5, 12.0, 12.2, or 12.3.
  3. Confirm the default reports feature is accessible
    Access the '/reports' or '/defaultReports' endpoint through the web interface without authentication to verify the vulnerable feature is exposed.
    Affected if The default reports feature is accessible without authentication.
  4. Check if the web interface is exposed to network
    Verify whether the Firewall Analyzer web console is accessible from untrusted networks or the internet by reviewing firewall rules or network ACLs allowing external access to ports 8080/8443.
    Affected if The web interface is reachable from untrusted networks.

You are affected if Zoho ManageEngine Firewall Analyzer versions 7.2 through 12.3 are installed AND the default reports feature is accessible to unauthenticated users on an exposed web interface.

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 123218 or later which contains the patched code to remediate the SQL injection vulnerability in the default reports feature.

Recommended fix High confidence

ManageEngine Firewall Analyzer 12.3 Build 123218 or later

  1. 1. Back up the current ManageEngine Firewall Analyzer installation and database before proceeding.
  2. 2. Download ManageEngine Firewall Analyzer version 12.3 Build 123218 or later from the official Zoho ManageEngine download center.
  3. 3. Stop the Firewall Analyzer service.
  4. 4. Install or upgrade to the downloaded version following the vendor's upgrade documentation.
  5. 5. Start the Firewall Analyzer service.
  6. 6. Verify the SQL injection vulnerability is remediated by testing the 'default reports' feature.
  7. 7. Confirm normal operations are functioning as expected.
Caveat Review vendor release notes for any configuration or feature changes between your current version and 12.3

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

Fix this in Manageengine Firewall Analyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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