# CVE-2022-33862: Improper access control mechanism in IPP

> Attackers can access vulnerable systems using default credentials, leading to unauthorized access and potential data exposure.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2024
- **Updated:** 25 Nov 2024
- **Also known as:** GHSA-4527-385c-q8r6

## What is CVE-2022-33862?

CVE-2022-33862 is a medium-severity vulnerability in Eaton Intelligent Power Protector (IPP), published on 25 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IPP software prior to v1.71 is vulnerable to default credential vulnerability. This could
lead attackers to identify and access vulnerable systems.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2022-33862 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33862 is a medium-severity vulnerability in Eaton Intelligent Power Protector (IPP), published on 25 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-33862 in the wild and no public exploit code.

Affected product: Eaton Intelligent Power Protector (IPP). 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-33862/ (Markdown: https://insights.sbomify.com/CVE-2022-33862/index.md)
```

## Sources

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

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