CVE-2023-23444
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 · uneditedMissing Authentication for Critical Function in SICK Flexi Classic and Flexi Soft Gateways with Partnumbers 1042193, 1042964, 1044078, 1044072, 1044073, 1044074, 1099830, 1099832, 1127717, 1069070, 1112296, 1051432, 1102420, 1127487, 1121596, 1121597 allows an unauthenticated remote attacker to influence the availability of the device by changing the IP settings of the device via broadcasted UDP packets.
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 confidenceMissing authentication in SICK Flexi Classic and Flexi Soft Gateways allows unauthenticated remote attackers to change device IP settings by sending broadcast UDP packets. This is a critical authentication bypass vulnerability affecting multiple gateway part numbers where the IP configuration interface lacks any access controls.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 SICK gateway device model on the networkInventory network devices to determine if any SICK Flexi Classic or Flexi Soft Gateways are present. Look for part numbers: Ue410 En4, Ue410 En3, Ue410 En1, Fx0 Gpnt00030, Fx0 Gpnt00010, Fx0 Gpnt00000, Fx0 Gmod00010, Fx0 Gmod00000Affected if The device matches one of the affected part numbers listed in the CVE
-
Confirm the firmware versionRetrieve the firmware version from the device or its management interface. Compare against the affected product listAffected if The device firmware is any version of the listed SICK gateway models (all versions are affected)
-
Check UDP port exposureScan the network for open UDP ports on the device, particularly ports commonly used for IP configuration or network management. Verify if UDP ports are accessible from untrusted network segmentsAffected if UDP ports used for IP configuration are open and accessible from network segments outside the trusted management zone
-
Assess network accessibilityDetermine if broadcast UDP packets can reach the device from any network segment. Check if the device is directly accessible on the network without authentication requirementsAffected if The device IP configuration interface accepts broadcast UDP packets without requiring any authentication
-
Verify network segmentationReview firewall rules and network ACLs to determine if the device's UDP management interfaces are protected from untrusted sourcesAffected if No firewall or network segmentation is in place to restrict UDP access to the device from untrusted sources
A user is affected if they have any SICK Flexi Classic or Flexi Soft Gateway device from the affected part number list, with UDP-based IP configuration interfaces exposed to untrusted network segments without authentication controls.
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 authentication for UDP-based IP configuration interfaces, or if firmware update is unavailable, deploy network segmentation and firewall rules to restrict UDP access to trusted sources only.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23444 — 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-2023-23444 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