dbcve.org
Application Insight ManagerApplication · Monitorapp

CVE-2021-36982

HIGH · 8.1 CVSS v3.1 Published 2021-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
AIMANAGER before B115 on MONITORAPP Application Insight Web Application Firewall (AIWAF) devices with Manager 2.1.0 allows OS Command Injection because of missing input validation on one of the parameters of an HTTP request.

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

OS Command Injection vulnerability in AIMANAGER (before version B115) on MONITORAPP Application Insight Web Application Firewall (AIWAF) devices with Manager 2.1.0. The vulnerability exists due to missing input validation on an HTTP request parameter, allowing remote attackers to inject and execute arbitrary operating system commands on the affected device.

MitigationUpdate AIMANAGER to version B115 or later. If immediate patching is not feasible, implement network access controls to restrict management interface exposure and deploy WAF rules to block command injection payloads.

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
Application Insight ManagerApplication
Affected:>= b107, < b115

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

CVSS:3.1/AV:N/AC:H/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 AIMANAGER version
    Locate the installed version of AIMANAGER (Monitorapp Application Insight Manager) on your AIWAF device. This is typically found in the product UI under About or System Information, or via command line if accessible. Compare the version number to the affected range: versions B107 through B114 are vulnerable; version B115 and later are not.
    Affected if The installed version is B107, B108, B109, B110, B111, B112, B113, or B114 (any version >= b107 but < b115).
  2. Confirm Manager component version
    Verify the version of the Manager component running on the device. The CVE specifies Manager 2.1.0 as part of the affected configuration. Check the Manager module version through the management interface or device documentation.
    Affected if Manager version 2.1.0 is installed alongside an affected AIMANAGER version in the B107-B114 range.
  3. Assess management interface exposure
    Determine if the AIWAF management interface is accessible from network segments outside your trusted internal network. This vulnerability is exploitable via HTTP request parameters, meaning the management service must be reachable over the network.
    Affected if The management interface is exposed to untrusted networks or the internet, allowing HTTP requests to reach the vulnerable parameter.
  4. Review access logs for injection patterns
    Examine AIWAF management interface access logs and HTTP request logs for suspicious patterns typical of command injection attempts. Look for shell metacharacters (such as ; | & $ ` or command syntax) in request parameters that should only contain benign input.
    Affected if Log analysis reveals command injection payloads in HTTP parameters targeting the management interface, indicating potential exploitation attempts.

You are affected if your AIMANAGER version is between B107 and B114 inclusive, your Manager component is version 2.1.0, and the management interface is network-accessible to send HTTP requests containing the vulnerable parameter.

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

Update AIMANAGER to version B115 or later. If immediate patching is not feasible, implement network access controls to restrict management interface exposure and deploy WAF rules to block command injection payloads.

Recommended fix High confidence

B115

  1. 1. Identify the current version of Application Insight Manager (AIMANAGER) by checking the system information or management interface.
  2. 2. Obtain the fixed version B115 from the official MONITORAPP vendor channels or support.
  3. 3. Follow MONITORAPP's official upgrade procedure for Application Insight Manager to update from the current version to version B115.
  4. 4. After upgrading, verify the system is running version B115 and confirm the vulnerability is remediated.

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

Fix this in Application Insight Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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