CVE-2020-2075: Platform mechanism AutoIP allows remote attackers to reboot the device via a crafted packet in SICK AG solutions Bulkscan LMS111, Bulkscan L
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 73.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Platform mechanism AutoIP allows remote attackers to reboot the device via a crafted packet in SICK AG solutions Bulkscan LMS111, Bulkscan LMS511, CLV62x – CLV65x, ICR890-3, LMS10x, LMS11x, LMS15x, LMS12x, LMS13x, LMS14x, LMS5xx, LMS53x, MSC800, RFH.
- Published
- Aug 31, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 73th percentile
- CWE
- CWE-703
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sick | lms111 firmware | cpe:2.3:o:sick:lms111_firmware |
| sick | lms111 | cpe:2.3:h:sick:lms111 |
| sick | lms511 firmware | cpe:2.3:o:sick:lms511_firmware |
| sick | lms511 | cpe:2.3:h:sick:lms511 |
| sick | clv620 firmware | cpe:2.3:o:sick:clv620_firmware |
| sick | clv620 | cpe:2.3:h:sick:clv620 |
| sick | clv622 firmware | cpe:2.3:o:sick:clv622_firmware |
| sick | clv622 | cpe:2.3:h:sick:clv622 |
| sick | clv621 firmware | cpe:2.3:o:sick:clv621_firmware |
| sick | clv621 | cpe:2.3:h:sick:clv621 |
| sick | icr890-3 firmware | cpe:2.3:o:sick:icr890-3_firmware |
| sick | icr890-3 | cpe:2.3:h:sick:icr890-3 |
and 48 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sick clv620 firmwareall versions
- sick clv621 firmwareall versions
- sick clv622 firmwareall versions
- sick clv630 firmwareall versions
- sick clv631 firmwareall versions
- sick clv632 firmwareall versions
- sick clv640 firmwareall versions
- sick clv642 firmwareall versions
- sick clv650 firmwareall versions
- sick clv651 firmwareall versions
- sick icr890-3 firmwareall versions
- sick icr890-3.5 firmwareall versions
- sick lms100 firmwarebefore 2.0
- sick lms101 firmwarebefore 2.0
- sick lms111 firmwarebefore 1.04
- sick lms111 firmwarebefore 2.0
- sick lms121 firmwarebefore 2.10
- sick lms122 firmwarebefore 2.10
- sick lms123 firmwarebefore 2.10
- sick lms131 firmwarebefore 2.10
Versions reported by the vendor
Affected version ranges reported by the assigning authority (SICK AG). Independent of NVD's CPE analysis and usually ahead of it.
n/a Bulkscan LMS111; Bulkscan LMS511; CLV62x – CLV65x; ICR890-3; LMS10x, LMS11x, LMS15x; LMS12x, LMS13x, LMS14x; LMS5xx, LMS53x; MSC800; RFH
- All Versions < V1.04, All Versions < V2.30, All versions with Ethernet interface, All ICR890-3 and ICR890-3.5 devices all versions, All Versions < V2.0, All Versions < V2.10, All versions, All Versions < V4.10affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-703 · Improper Check or Handling of Exceptional ConditionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.