CVE-2021-27858
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 · uneditedA missing authorization vulnerability in the web management interface of FatPipe WARP, IPVPN, and MPVPN software prior to versions 10.1.2r60p91 and 10.2.2r42 allows a remote attacker to access at least the URL "/fpui/jsp/index.jsp" leading to unknown impact, presumably some violation of confidentiality. Older versions of FatPipe software may also be vulnerable. The FatPipe advisory identifier for this vulnerability is FPSA004.
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 missing authorization vulnerability in the web management interface of FatPipe WARP, IPVPN, and MPVPN allows unauthenticated remote attackers to access the management URL '/fpui/jsp/index.jsp' without proper authentication, potentially leading to unauthorized access to the device management console and confidentiality violations.
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.2.0= 6.1.2= 7.1.2= 9.1.2= 10.1.2= 10.2.2= 5.2.0= 6.1.2= 7.1.2= 9.1.2= 10.1.2= 10.2.2= 5.2.0= 6.1.2= 7.1.2= 9.1.2= 10.1.2= 10.2.2CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Confirm FatPipe device typeAccess the device web interface or CLI and identify the model (WARP, IPVPN, or MPVPN). This can typically be done via the login page, device status page, or CLI command like 'show system info'.Affected if The device is a FatPipe WARP, IPVPN, or MPVPN model.
-
Check installed firmware versionLocate the firmware version in the device web interface (usually under System Status, About, or Maintenance) or via CLI command such as 'show version' or 'get firmware version'. Compare the version number against the affected list: 5.2.0, 6.1.2, 7.1.2, 9.1.2, 10.1.2, or 10.2.2.Affected if The installed firmware version matches exactly one of these: 5.2.0, 6.1.2, 7.1.2, 9.1.2, 10.1.2, or 10.2.2.
-
Test unauthenticated access to management URLAttempt to access the endpoint '/fpui/jsp/index.jsp' directly via HTTP/HTTPS without providing any login credentials. For example: http://[device-ip]/fpui/jsp/index.jsp or https://[device-ip]/fpui/jsp/index.jsp.Affected if The page loads successfully and displays the management console or login interface without requiring authentication.
-
Verify management interface exposureCheck if the web management interface is accessible from untrusted networks (such as directly from the internet or untrusted VLANs) by attempting access from an external IP or non-management network segment.Affected if The device management interface (port 80/443 or custom management ports) is reachable from untrusted networks without VPN or firewall restrictions.
If the device is a FatPipe WARP, IPVPN, or MPVPN running firmware version 5.2.0, 6.1.2, 7.1.2, 9.1.2, 10.1.2, or 10.2.2 AND the /fpui/jsp/index.jsp endpoint is accessible without authentication from an untrusted network, the environment is affected by CVE-2021-27858.
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 to FatPipe versions 10.1.2r60p91, 10.2.2r42 or later. If immediate patching is not feasible, restrict network access to the management interface using firewall rules or VPN tunnels to prevent unauthorized external access.
10.1.2r60p91 or 10.2.2r42
- Identify the current FatPipe firmware version (WARP, IPVPN, or MPVPN) running on the device
- Navigate to FatPipe's official support or download page (www.fatpipeinc.com) to obtain the fixed firmware version
- Download firmware version 10.1.2r60p91 or 10.2.2r42 (whichever is compatible with your device model)
- Follow FatPipe's standard firmware upgrade procedure documented in the product manual to apply the update
- After upgrading, verify the version change was successful and test that the /fpui/jsp/index.jsp URL now requires proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27858 — 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-27858 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