CVE-2023-5102
MEDIUMCVSS 5.3/10EPSS 0.57%
Last modified
CVE-2023-5102 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. Insufficient Control Flow Management in RDT400 in SICK APU allows an unprivileged remote attacker to potentially enable hidden functionality via HTTP requests. . EPSS estimates a 0.57% chance of exploitation in the next 30 days.
Description
Insufficient Control Flow Management in RDT400 in SICK APU allows an unprivileged remote attacker to potentially enable hidden functionality via HTTP requests.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Sick | Apu0200 Firmware | < 4.0.0.6 |
References
- https://sick.com/psirtProduct
- https://sick.com/psirtProduct
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-5102?
Insufficient Control Flow Management in RDT400 in SICK APU allows an unprivileged remote attacker to potentially enable hidden functionality via HTTP requests.
How severe is CVE-2023-5102?
CVE-2023-5102 has a CVSS score of 5.3/10 (MEDIUM severity). The EPSS model estimates a 0.57% probability of exploitation in the next 30 days.
How do I fix CVE-2023-5102?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-51014TOTOLINK EX1800T V9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51015TOTOLINX EX1800T v9.1.0cu.2112_B20220316 is vulnerable to ar…9.8
- CVE-2023-51016TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51017TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51018TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51019TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51020TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51021TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51022TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51023TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to ar…9.8
- CVE-2023-51024TOTOlink EX1800T v9.1.0cu.2112_B20220316 is vulnerable to un…9.8
- CVE-2023-51025TOTOlink EX1800T V9.1.0cu.2112_B20220316 is vulnerable to an…9.8
Are you affected by CVE-2023-5102?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST