The Dataprobe cloud usernames and passwords are stored in plain text in a specific file.
Noroxi assessment
Priority: Monitor (action score 26/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.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. 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
The Dataprobe cloud usernames and passwords are stored in plain text in a specific file. Any user able to read this specific file from the device could compromise other devices connected to the user's cloud.
- Published
- May 22, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 6th percentile
- CWE
- CWE-256
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · icscert
- 6.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
|---|---|---|
| dataprobe | iboot-pdu4-n20 firmware | cpe:2.3:o:dataprobe:iboot-pdu4-n20_firmware |
| dataprobe | iboot-pdu4-n20 | cpe:2.3:h:dataprobe:iboot-pdu4-n20 |
| dataprobe | iboot-pdu4sa-n15 firmware | cpe:2.3:o:dataprobe:iboot-pdu4sa-n15_firmware |
| dataprobe | iboot-pdu4sa-n15 | cpe:2.3:h:dataprobe:iboot-pdu4sa-n15 |
| dataprobe | iboot-pdu4a-n15 firmware | cpe:2.3:o:dataprobe:iboot-pdu4a-n15_firmware |
| dataprobe | iboot-pdu4a-n15 | cpe:2.3:h:dataprobe:iboot-pdu4a-n15 |
| dataprobe | iboot-pdu4sa-n20 firmware | cpe:2.3:o:dataprobe:iboot-pdu4sa-n20_firmware |
| dataprobe | iboot-pdu4sa-n20 | cpe:2.3:h:dataprobe:iboot-pdu4sa-n20 |
| dataprobe | iboot-pdu4a-n20 firmware | cpe:2.3:o:dataprobe:iboot-pdu4a-n20_firmware |
| dataprobe | iboot-pdu4a-n20 | cpe:2.3:h:dataprobe:iboot-pdu4a-n20 |
| dataprobe | iboot-pdu8sa-n15 firmware | cpe:2.3:o:dataprobe:iboot-pdu8sa-n15_firmware |
| dataprobe | iboot-pdu8sa-n15 | cpe:2.3:h:dataprobe:iboot-pdu8sa-n15 |
and 32 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dataprobe iboot-pdu4-c20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4-n20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4a-c10 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4a-c20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4a-n15 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4a-n20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4sa-c10 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4sa-c20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4sa-n15 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu4sa-n20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8a-2c10 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8a-2c20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8a-2n15 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8a-2n20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8a-c10 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8a-c20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8a-n15 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8a-n20 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8sa-2n15 firmwarebefore 1.42.06162022
- dataprobe iboot-pdu8sa-c10 firmwarebefore 1.42.06162022
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
Dataprobe, Inc. Dataprobe iBoot-PDU FW
- before 1.42.06162022affected
Same product
dataprobe: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-3184Dataprobe iBoot-PDU FW versions prior to 1.42.06162022 contain a vulnerability where the device’s existing firmware allows unauthenticated u42Plan
- CVE-2022-46738The affected product exposes multiple sensitive data fields of the affected product.39Monitor
- CVE-2022-46658The affected product is vulnerable to a stack-based buffer overflow which could lead to a denial of service or remote code execution.39Monitor
- CVE-2022-3183Dataprobe iBoot-PDU FW versions prior to 1.42.06162022 contain a vulnerability where a specific function does not sanitize the input provide39Monitor
- CVE-2022-47311A proprietary protocol for iBoot devices is used for control and keepalive commands.35Monitor
- CVE-2022-47320The iBoot device’s basic discovery protocol assists in initial device configuration.32Monitor
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- A low-privileged account is enough.
- 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-256 · Plaintext Storage of a PasswordCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.