# CVE-2022-22813: Hardcoded credentials in Easergy P40 Series model numbers with Ethernet option bit as Q, R, S (All PX4X firmware Versions)

> Hardcoded TLS credentials allow attackers to intercept and manipulate traffic in the Courier tunneling network of Easergy P40 devices.

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

## What is CVE-2022-22813?

CVE-2022-22813 is a critical vulnerability in Easergy P40 Series model numbers with Ethernet option bit as Q, R, S (All PX4X firmware Versions), published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CWE-798: Use of Hard-coded Credentials vulnerability exists. If an attacker were to obtain the TLS cryptographic key and take active control of the Courier tunneling communication network, they could potentially observe and manipulate traffic associated with product configuration.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 33 products.


Products: Schneider-Electric Easergy P141 Firmware, Schneider-Electric Easergy P142 Firmware, Schneider-Electric Easergy P143 Firmware, Schneider-Electric Easergy P145 Firmware, Schneider-Electric Easergy P241 Firmware, Schneider-Electric Easergy P242 Firmware, Schneider-Electric Easergy P243 Firmware, Schneider-Electric Easergy P341 Firmware, Schneider-Electric Easergy P342 Firmware, Schneider-Electric Easergy P343 Firmware, Schneider-Electric Easergy P344 Firmware, Schneider-Electric Easergy P345 Firmware, Schneider-Electric Easergy P441 Firmware, Schneider-Electric Easergy P442 Firmware, Schneider-Electric Easergy P443 Firmware, Schneider-Electric Easergy P444 Firmware, Schneider-Electric Easergy P445 Firmware, Schneider-Electric Easergy P446 Firmware, Schneider-Electric Easergy P541 Firmware, Schneider-Electric Easergy P542 Firmware and 13 more.

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

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

## Is CVE-2022-22813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22813 is a critical vulnerability in Easergy P40 Series model numbers with Ethernet option bit as Q, R, S (All PX4X firmware Versions), published on 9 Feb 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-22813 in the wild and no public exploit code.

Affected product: Easergy P40 Series model numbers with Ethernet option bit as Q, R, S (All PX4X firmware Versions). 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-22813/ (Markdown: https://insights.sbomify.com/CVE-2022-22813/index.md)
```

## Sources

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

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