FortiproxyApplication · Fortinet
CVE-2022-41331
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 authentication for critical function vulnerability [CWE-306] in FortiPresence infrastructure server before version 1.2.1 allows a remote, unauthenticated attacker to access the Redis and MongoDB instances via crafted authentication requests.
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 confidenceA missing authentication vulnerability in FortiPresence infrastructure server versions before 1.2.1 allows remote, unauthenticated attackers to access underlying Redis and MongoDB database instances by sending crafted authentication requests. This critical flaw (CWE-306) exposes sensitive data stored in these databases without requiring any valid credentials.
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
FortiproxyApplication
>= 1.0.0, < 2.0.0CVSS 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.
-
Identify Fortiproxy versionCheck the installed Fortiproxy version using the command 'fortiproxy --version' or review the system package manager for the installed package version.Affected if The installed version is >= 1.0.0 and < 2.0.0, placing it within the vulnerable range.
-
Confirm FortiPresence infrastructure server is runningCheck for running FortiPresence services using 'ps aux | grep -i fortipresence' or review the service manager for fortipresence-infrastructure or similar processes.Affected if FortiPresence infrastructure server processes are running on the system.
-
Check Redis port exposureInspect network listeners using 'netstat -tlnp | grep 6379' or 'ss -tlnp | grep 6379' to determine if Redis port 6379 is bound to a network interface accessible from external sources.Affected if Redis port 6379 is listening on a non-loopback interface (0.0.0.0 or external IP) and is reachable from untrusted networks.
-
Check MongoDB port exposureInspect network listeners using 'netstat -tlnp | grep 27017' or 'ss -tlnp | grep 27017' to determine if MongoDB port 27017 is bound to a network interface accessible from external sources.Affected if MongoDB port 27017 is listening on a non-loopback interface and is reachable from untrusted networks.
-
Verify database authentication configurationReview Redis and MongoDB configuration files (typically redis.conf and mongod.conf) to confirm whether password authentication or other authentication mechanisms are enabled and enforced.Affected if Database authentication is disabled, not enforced, or allows empty/null credentials.
You are affected if Fortiproxy version is between 1.0.0 and 2.0.0 AND FortiPresence infrastructure server is running with exposed Redis or MongoDB ports accessible from untrusted networks without proper authentication enforcement.
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 · scoped2.0.0
Upgrade FortiPresence infrastructure server to version 1.2.1 or later to implement proper authentication. Until patched, restrict network access to Redis and MongoDB ports via firewall rules and implement network segmentation to limit exposure.
FortiPresence version 1.2.1 or later (note: the affected versions field lists Fortiproxy but the description references FortiPresence; if Fortiproxy is the actual product, upgrade to version 2.0.0 or later)
- 1. Identify the current FortiPresence infrastructure server version installed.
- 2. Download FortiPresence version 1.2.1 or later from Fortinet's official support portal.
- 3. Review Fortinet's upgrade documentation for FortiPresence.
- 4. Schedule a maintenance window to perform the upgrade.
- 5. Back up the current configuration and database data.
- 6. Upgrade FortiPresence to version 1.2.1 or the latest available stable version.
- 7. Verify the upgrade was successful and the service is running.
- 8. Confirm the vulnerability is resolved by checking that authentication is now required for Redis and MongoDB access.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiproxy
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing6.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 $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41331 — 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-2022-41331 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