Basic Pdu Firmware: Incorrect Authorization
CVE-2022-33174 is a high-severity incorrect authorization vulnerability in Basic Pdu Firmware from Powertekpdus, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 3.30.30 as the first without the flaw, so updating Basic Pdu Firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 14.1% chance of exploitation within 30 days, which is in the top 3.37% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Update Basic Pdu Firmware to 3.30.30 or a later version.
- Update Pm Pdu Firmware to 3.30.30 or a later version.
- Update Piml Pdu Firmware to 3.30.30 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Powertekpdus | Basic Pdu Firmware | before 3.30.30 | 3.30.30 |
| Powertekpdus | Pm Pdu Firmware | before 3.30.30 | 3.30.30 |
| Powertekpdus | Piml Pdu Firmware | before 3.30.30 | 3.30.30 |
| Powertekpdus | Smart Pim Firmware | before 3.30.30 | 3.30.30 |
| Powertekpdus | Smart Pos Firmware | before 3.30.30 | 3.30.30 |
| Powertekpdus | Smart Pom Firmware | before 3.30.30 | 3.30.30 |
| Powertekpdus | Smart Poms Firmware | before 3.30.30 | 3.30.30 |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | CNA (mitre.org) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
Power Distribution Units running on Powertek firmware (multiple brands) before 3.30.30 allows remote authorization bypass in the web interface. To exploit the vulnerability, an attacker must send an HTTP packet to the data retrieval interface (/cgi/get_param.cgi) with the tmpToken cookie set to an empty string followed by a semicolon. This bypasses an active session authorization check. This can be then used to fetch the values of protected sys.passwd and sys.su.name fields that contain the username and password in cleartext.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- gynvael.coldwind.pl/?lang=en&id=748Exploit, Third Party Advisory
Other vulnerabilities in Basic Pdu Firmware
- 9.8 Critical severity
Recent Incorrect Authorization vulnerabilities
- 7.1 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.