dbcve.org
Flx3 Cpuc1 FirmwareOperating system · Sick

CVE-2022-27583

CRITICAL · 9.1 CVSS v3.1 Published 2022-10-31
Fix available
A fix is available. Upgrade to 1.10.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A remote unprivileged attacker can interact with the configuration interface of a Flexi-Compact FLX3-CPUC1 or FLX3-CPUC2 running an affected firmware version to potentially impact the availability of the FlexiCompact.

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 confidence

A remote unauthenticated attacker can access the configuration interface of Flexi-Compact FLX3-CPUC1 or FLX3-CPUC2 controllers running affected firmware versions. The vulnerability allows interaction with the config interface to potentially impact system availability, likely through denial-of-service conditions given the CVSS availability impact metric.

MitigationNetwork-segment the affected devices and restrict access to the configuration interface to only trusted management networks; implement firewall rules to limit exposure to authorized personnel until vendor firmware updates are available.

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
Flx3 Cpuc1 FirmwareOperating system
Affected:< 1.10.0
Flx3 Cpuc2 FirmwareOperating system
Affected:< 1.10.0

CVSS 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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the physical device or check inventory/scm systems for Sick Flexi-Compact controllers. Confirm the model is either FLX3-CPUC1 or FLX3-CPUC2.
    Affected if Device model is FLX3-CPUC1 or FLX3-CPUC2 and firmware version is below 1.10.0
  2. Check the installed firmware version
    Access the controller web interface, use the SICK Manager tool, or query the device via its management interface to retrieve the current firmware version.
    Affected if Firmware version is less than 1.10.0 (e.g., 1.09.x, 1.08.x, etc.)
  3. Verify if the configuration interface is network accessible
    Attempt to reach the device configuration interface over the network on typical management ports (HTTP/HTTPS typically ports 80/443). Check if the /config or similar endpoint responds without authentication.
    Affected if The configuration interface is reachable over the network without authentication credentials
  4. Assess network exposure of the device
    Review network segmentation, firewall rules, and access control lists to determine if the device management interface is exposed to untrusted or external networks.
    Affected if The controller is accessible from untrusted networks or the internet rather than only from a trusted management VLAN

You are affected if you have a Sick FLX3-CPUC1 or FLX3-CPUC2 controller running firmware version below 1.10.0 with its configuration interface accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.10.0 or later
Fixed in 1.10.0
Interim mitigation

Network-segment the affected devices and restrict access to the configuration interface to only trusted management networks; implement firewall rules to limit exposure to authorized personnel until vendor firmware updates are available.

Recommended fix Moderate confidence

Firmware version 1.10.0 or later for FLX3-CPUC1 and FLX3-CPUC2

  1. Identify the affected device model (FLX3-CPUC1 or FLX3-CPUC2) in the industrial network
  2. Check the current firmware version of the affected device
  3. Navigate to sick.com support portal and locate the firmware download section for Flexi-Compact FLX3-CPUC devices
  4. Download firmware version 1.10.0 or later for the specific device model
  5. Follow SICK AG's standard firmware update procedure (typically via SICK Service Interface or web-based management)
  6. After upgrade, verify the new firmware version is 1.10.0 or higher
  7. Confirm the configuration interface is accessible only to authorized users
Caveat Review SICK release notes for 1.10.0 to check for any configuration or functionality changes that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flx3 Cpuc1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27583 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27583 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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