The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier is vulnerable to authentication bypass.
Noroxi assessment
Priority: Monitor (action score 39/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.95% (FIRST EPSS); higher than 60.5% 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 CISA the attack is automatable: targets can be found by mass scanning.
- 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
The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier is vulnerable to authentication bypass. By manipulating the IP address field in the "iBootPduSiteAuth" cookie, a malicious agent can direct the device to connect to a rouge database.Successful exploitation allows the malicious agent to take actions with administrator privileges including, but not limited to, manipulating power levels, modifying user accounts, and exporting confidential user information
- Published
- Aug 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 60th percentile
- CWE
- CWE-502
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · trellix
- 9.8
- 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-pdu4a-c10 firmware | cpe:2.3:o:dataprobe:iboot-pdu4a-c10_firmware |
| dataprobe | iboot-pdu4a-c10 | cpe:2.3:h:dataprobe:iboot-pdu4a-c10 |
| dataprobe | iboot-pdu4a-c20 firmware | cpe:2.3:o:dataprobe:iboot-pdu4a-c20_firmware |
| dataprobe | iboot-pdu4a-c20 | cpe:2.3:h:dataprobe:iboot-pdu4a-c20 |
| 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-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-pdu4-c20 firmware | cpe:2.3:o:dataprobe:iboot-pdu4-c20_firmware |
| dataprobe | iboot-pdu4-c20 | cpe:2.3:h:dataprobe:iboot-pdu4-c20 |
| 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 |
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.44.0804202
- dataprobe iboot-pdu4-n20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu4a-c10 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu4a-c20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu4a-n15 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu4a-n20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu4sa-c10 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu4sa-c20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu4sa-n15 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu4sa-n20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8a-2c10 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8a-2c20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8a-2n15 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8a-2n20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8a-c10 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8a-c20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8a-n15 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8a-n20 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8sa-2n15 firmwarebefore 1.44.0804202
- dataprobe iboot-pdu8sa-c10 firmwarebefore 1.44.0804202
Versions reported by the vendor
Affected version ranges reported by the assigning authority (trellix). Independent of NVD's CPE analysis and usually ahead of it.
Dataprobe iBoot PDU
- 1.43.03312023 and later · up to and including <= 1.43.03312023affected
Same product
dataprobe: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-3264The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier uses hard-coded credentials for all interactions with the internal39Monitor
- CVE-2023-3260The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier is vulnerable to command injection via the `user-name` URL paramet35Monitor
- CVE-2023-3263The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier is vulnerable to authentication bypass in the REST API due to the 30Monitor
- CVE-2023-3261The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier contains a buffer overflow vulnerability in the librta.so.0.0.0 li28Monitor
- CVE-2023-3262The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier uses hard-coded credentials for all interactions with the internal26Monitor
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.
- Philippe LaulheretCisco Talosreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2023-32600 days apartThe Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier is vulnerable to command injection via the `user-name` URL paramet35Monitor
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)job = pickle.loads(payload)Fixed
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig): raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.