CVE-2021-36921
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 · uneditedAIMANAGER before B115 on MONITORAPP Application Insight Web Application Firewall (AIWAF) devices with Manager 2.1.0 has Improper Authentication. An attacker can gain administrative access by modifying the response to an authentication check 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 · high confidenceThe AIMANAGER component in MONITORAPP AIWAF devices with Manager 2.1.0 contains an improper authentication vulnerability. An attacker can intercept and modify the response to an authentication check request, bypassing authentication entirely and gaining administrative access to the device.
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>= b107, < b115CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed AIMANAGER versionAccess the device management console or check the software package version. The version is typically displayed in the system information page of the Application Insight Manager web interface, or can be retrieved via CLI command such as 'show system-info' or 'aiwaf-manager version'. Compare the version string (b107, b108, etc.) against the affected range.Affected if The installed version is b107, b108, b109, b110, b111, b112, b113, or b114 (any version >= b107 but < b115)
-
Confirm AIMANAGER web interface is accessibleVerify that the Application Insight Manager management web interface (typically ports 443 or 8443) is reachable from the network. This can be checked via browser access, curl/wget to the management URL, or network port scan.Affected if The management interface is exposed on the network and responds to authentication requests
-
Check for unauthorized administrative accountsReview the list of configured administrative users in the AIMANAGER user management section. Look for any unknown or unexpected accounts with administrative privileges that may indicate the vulnerability was exploited.Affected if There are administrative accounts that were not created by legitimate administrators
-
Review authentication logs for anomaliesExamine AIMANAGER authentication and access logs for unusual patterns: successful logins from unexpected IP addresses, sessions that bypassed credential verification, or multiple authentication bypass indicators. These logs are typically found in /var/log/aiwaf/ or via the manager logs interface.Affected if Logs show authentication bypass events, unexpected admin sessions, or successful logins without proper credential submission
The environment is affected if AIMANAGER version is b107 through b114 AND the management web interface is network-accessible, regardless of whether the vulnerability has been exploited.
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 · scopedUpgrade AIMANAGER to version B115 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the management interface and monitor for unauthorized administrative access.
b115
- Identify the current version of Application Insight Manager by accessing the device management interface or checking system information
- Create a full backup of the current AIMANAGER configuration to preserve settings
- Download AIMANAGER version b115 or later from the official MONITORAPP source (www.monitorapp.com)
- Access the AIMANAGER administrative interface and navigate to the firmware/software update section
- Upload and apply the b115 (or later) version upgrade package
- Allow the upgrade process to complete and verify the system restarts properly
- Confirm the new version b115 is installed by checking the system information
- Test that authentication functions correctly with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36921 — 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-2021-36921 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