The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier uses hard-coded credentials for all interactions with the internal
The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier uses hard-coded credentials for all interactions with the internal Postgres database.A malicious agent with the ability to execute operating system commands on the device can leverage this vulnerability to read, modify, or delete arbitrary database records.
- Published
- Aug 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 21th percentile
- CWE
- CWE-798
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.7
- CNA · trellix
- 6.7
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| 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-3259The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier is vulnerable to authentication bypass.39Monitor
- 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
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.
- Jesse Chickreporter
- Sam QuinnMcAfee Enterprise ATRreporter
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.
- Administrator privileges are 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
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-798 · Use of Hard-coded CredentialsCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
For convenience in support or manufacturing, an account that is identical on every device is embedded in the software. Credentials learned from one device work on all of them.
The bug in code
The whole CWE-798 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const SUPPORT_USER = "support";const SUPPORT_PASS = "hardcoded-password";Fixed
const creds = await provisioning.deviceCredentials(deviceId);if (creds.mustRotate) await forcePasswordChange(deviceId);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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.