CVE-2022-32516
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 CWE-352: Cross-Site Request Forgery (CSRF) vulnerability exists that could cause system’s configurations override and cause a reboot loop when the product suffers from POST-Based Cross-Site Request Forgery (CSRF). Affected Products: Conext™ ComBox (All Versions)
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 POST-based Cross-Site Request Forgery (CSRF) vulnerability in the Conext ComBox device allows authenticated attackers to send crafted requests that override system configurations, potentially triggering a persistent reboot loop that renders the device inoperable.
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 dataall versionsCVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 device modelAccess the device web interface or check the device label/metadata to confirm it is a Schneider Electric Conext ComBox device.Affected if The device is confirmed to be a Schneider Electric Conext ComBox.
-
Check firmware versionNavigate to the device web interface settings or use the device's administrative console to view the installed firmware version.Affected if Any firmware version is installed (all versions are affected per the CVE).
-
Inspect web form responses for anti-CSRF tokensUse a browser developer tool or HTTP proxy to capture a POST request response from the device web interface. Examine the HTML forms to determine if hidden anti-CSRF token fields are present in state-changing operations (e.g., configuration save, system reboot).Affected if Forms lack anti-CSRF token fields or tokens are missing from POST requests.
-
Inspect session cookies for SameSite attributeCapture HTTP responses from the device and examine the Set-Cookie headers for session cookies. Check if the SameSite attribute is set to 'Strict' or 'Lax'.Affected if Cookies do not have SameSite attribute set, or it is set to 'None' without the Secure flag.
-
Verify network-level CSRF protectionsCheck if a WAF, proxy, or network security device is configured with rules to validate the Origin/Referer headers and block unauthorized cross-site requests to the device web interface.Affected if No network-level CSRF protections are in place.
The environment is affected if it contains a Schneider Electric Conext ComBox device with a web interface that lacks anti-CSRF tokens in POST forms and does not have SameSite cookie attributes or network-level CSRF mitigations configured.
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.
From vendor dataImplement anti-CSRF tokens for all state-changing operations and configure SameSite cookie attributes; network-level CSRF protections (e.g., WAF rules) may provide interim mitigation until vendor patch is available.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32516 — 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-32516 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