Every applicability statement published about this vulnerability, kept as each source wrote it rather than merged into one verdict. Where sources disagree, both positions are shown.
A statement that names no version covers the whole product, which is not the same as your version falling inside a range. Orderings marked best effort come from schemes with no published comparison algorithm; exact ones follow a published specification.
Precedence decides which claim wins when two sources describe the same product over the same version range. It is a property of the source, not of the claim, and changing it re-ranks the data without re-reading a single document.
| Product | Status | Versions | Remediation | Source | |
|---|---|---|---|---|---|
| Rockwell Automation/ControlLogix® 5570 Rockwell Automation · ControlLogix® 5570 | affected | 20.011 | none available | cve_cna | |
| Rockwell Automation/ControlLogix® 5570 redundant Rockwell Automation · ControlLogix® 5570 redundant | affected | 20.054_kit1 | none available | cve_cna | |
| Rockwell Automation/GuardLogix® 5570 Rockwell Automation · GuardLogix® 5570 | affected | 20.011 | none available | cve_cna | |
| rockwellautomation/controllogix_5570_controller_firmware rockwellautomation · controllogix_5570_controller_firmware | affected | 20.011 | none available | cve_adp | |
| rockwellautomation/controllogix_5570_redundant_controller_firmware rockwellautomation · controllogix_5570_redundant_controller_firmware | affected | 20.054_kit1 | none available | cve_adp | |
| rockwellautomation/guardlogix_5570_controller_firmware rockwellautomation · guardlogix_5570_controller_firmware | affected | 20.011 | none available | cve_adp |
A claim with no version range is shown as written rather than expanded: a government catalog naming only a vendor and product is a real statement at zero granularity, and inventing bounds for it would put precision in the record that the source never offered.