# CVE-2022-33175: Information disclosure in n/a

> Attackers can steal administrator session IDs via an insecure API, enabling unauthorized access to read passwords and reconfigure the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-x3x3-7q8c-m397

## What is CVE-2022-33175?

CVE-2022-33175 is a critical vulnerability in n/a, published on 13 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Power Distribution Units running on Powertek firmware (multiple brands) before 3.30.30 have an insecure permissions setting on the user.token field that is accessible to everyone through the /cgi/get_param.cgi HTTP API. This leads to disclosing active session ids of currently logged-in administrators. The session id can then be reused to act as the administrator, allowing reading of the cleartext password, or reconfiguring the device.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2022-33175?

It affects 7 products.


Products: Powertekpdus Basic Pdu Firmware, Powertekpdus Piml Pdu Firmware, Powertekpdus Pm Pdu Firmware, Powertekpdus Smart Pim Firmware, Powertekpdus Smart Pom Firmware, Powertekpdus Smart Poms Firmware, Powertekpdus Smart Pos Firmware.

## How do I fix CVE-2022-33175?

No fix has been published for CVE-2022-33175 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-33175 being exploited?

There is no known exploitation of CVE-2022-33175 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-33174](https://insights.sbomify.com/CVE-2022-33174/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-33175 and fix it if it is affected.

What it is: CVE-2022-33175 is a critical vulnerability in n/a, published on 13 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-33175 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-33175/ (Markdown: https://insights.sbomify.com/CVE-2022-33175/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-33175
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-33175
- OSV: https://osv.dev/vulnerability/CVE-2022-33175

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-33175/
Summaries are generated and may contain mistakes; the official description above is the record.