CVE-2021-40091
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 · uneditedAn SSRF issue was discovered in SquaredUp for SCOM 5.2.1.6654.
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 confidenceA Server-Side Request Forgery (SSRF) vulnerability in SquaredUp for SCOM version 5.2.1.6654 allows remote attackers to induce the application to make arbitrary HTTP requests to internal infrastructure, potentially accessing sensitive internal services or performing port scanning of internal networks.
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< 5.3.1CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the installed SquaredUp for SCOM versionCheck the application's About page, installation directory, or the web interface footer which typically displays the version numberAffected if The version displayed is earlier than 5.3.1 (such as 5.2.1.6654 or any version below 5.3.1)
-
Verify the exact version from installation filesInspect the installation logs, thebin directory, or the web.config file in the SquaredUp installation folder for version metadataAffected if The version recorded in configuration files or logs is less than 5.3.1
-
Identify web endpoints that accept user-supplied URLsReview the SquaredUp web application's available dashboards, plugins, or integration features that could accept external URL inputs (such as web content widgets, API integrations, or monitoring connectors)Affected if Any feature accepting URLs is accessible and configurable by users
-
Confirm network accessibility of the applicationDetermine if the SquaredUp web interface is exposed to network users or external attackers who could supply malicious URLsAffected if The application is reachable by untrusted users who could trigger arbitrary HTTP requests through it
You are affected if SquaredUp for SCOM is installed at a version lower than 5.3.1 and the application has features accessible to attackers that accept URL inputs, allowing them to induce the server to make requests to internal infrastructure.
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 · scoped5.3.1
Upgrade SquaredUp for SCOM to the vendor-provided patched version. If an immediate patch is unavailable, restrict network access to the application and implement URL validation/allow-listing as a compensating control.
5.3.1 or later
- 1. Back up your current SquaredUp for SCOM installation and database
- 2. Review the SquaredUp 5.3 release notes and upgrade guide at support.squaredup.com for any pre-upgrade requirements
- 3. Upgrade your SquaredUp for SCOM installation to version 5.3.1 or later
- 4. After upgrade, verify the application is functioning correctly
- 5. Confirm the SSRF vulnerability is remediated by testing that the affected functionality no longer allows unauthorized server-side requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40091 — 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-40091 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