CVE-2020-11952: An issue was discovered on Rittal PDU-3C002DEC through 5.17.10 and CMCIII-PU-9333E0FB through 3.17.10 devices.
Noroxi assessment
Priority: Monitor (action score 24/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: 0.52% (FIRST EPSS).
- Someone with local access to the system 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
An issue was discovered on Rittal PDU-3C002DEC through 5.17.10 and CMCIII-PU-9333E0FB through 3.17.10 devices. Attackers can bypass the CLI menu.
- Published
- Jul 14, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- —
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
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 |
|---|---|---|
| rittal | cmciii-pu-9333e0fb firmware | cpe:2.3:o:rittal:cmciii-pu-9333e0fb_firmware |
| rittal | cmciii-pu-9333e0fb | cpe:2.3:h:rittal:cmciii-pu-9333e0fb |
| rittal | pdu-3c002dec firmware | cpe:2.3:o:rittal:pdu-3c002dec_firmware |
| rittal | pdu-3c002dec | cpe:2.3:h:rittal:pdu-3c002dec |
| rittal | cmc iii pu 7030.000 firmware | cpe:2.3:o:rittal:cmc_iii_pu_7030.000_firmware |
| rittal | cmc iii pu 7030.000 | cpe:2.3:h:rittal:cmc_iii_pu_7030.000 |
| rittal | lcp-cw firmware | cpe:2.3:o:rittal:lcp-cw_firmware |
| rittal | lcp-cw | cpe:2.3:h:rittal:lcp-cw |
| rittal | iot interface 3124.300 | cpe:2.3:a:rittal:iot_interface_3124.300 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rittal cmc iii pu 7030.000 firmwareup to 3.15.70_4 inclusive
- rittal cmciii-pu-9333e0fb firmwareup to 3.17.10 inclusive
- rittal iot interface 3124.300up to 6.17.00 inclusive
- rittal lcp-cw firmwareup to 3.15.70_4 inclusive
- rittal pdu-3c002dec firmwareup to 5.17.10 inclusive
Same product
rittal: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-11956An issue was discovered on Rittal PDU-3C002DEC through 5.17.10 and CMCIII-PU-9333E0FB through 3.17.10 devices.39Monitor
- CVE-2020-11951An issue was discovered on Rittal PDU-3C002DEC through 5.17.10 and CMCIII-PU-9333E0FB through 3.17.10 devices.39Monitor
- CVE-2020-11953An issue was discovered on Rittal PDU-3C002DEC through 5.15.40 and CMCIII-PU-9333E0FB through 3.15.70_4 devices.36Monitor
Published before and after this one in the same product
- Later →CVE-2020-11955Jul 14, 2020 · An issue was discovered on Rittal PDU-3C002DEC through 5.15.70 and CMCIII-PU-9333E0FB through 3.15.70 devices.35Monitor
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
- Someone with local access to the system 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
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.