CVE-2022-22813
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability involves hard-coded TLS cryptographic credentials embedded in the product's Courier tunneling communication network. An attacker who obtains these embedded TLS keys and gains active control of the network infrastructure could intercept and manipulate product configuration traffic. The CVSS 9.8 rating reflects the critical severity of credential-based remote exploitation leading to traffic manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device modelAccess the device management interface or use SNMP/management protocol to query the device model identifier. Verify it matches one of: Easergy P141, P142, P143, P145, P241, P242, P243, or P342.Affected if The device is any of the listed Easergy models (all versions affected)
-
Verify Courier tunneling is enabledCheck the device configuration for Courier tunneling protocol settings. This is typically found in the communication or network settings menu of the device web interface or management console.Affected if Courier tunneling communication feature is configured and active
-
Locate TLS credential storageExamine configuration backups, firmware image files, or exported device configurations for embedded TLS keys, certificates, or cryptographic material. Look for static key files or hard-coded credential blobs in the Courier-related configuration sections.Affected if Hard-coded TLS keys, certificates, or static cryptographic credentials are found embedded in configuration or firmware files
-
Inspect Courier network trafficIf you have network access, capture and inspect TLS traffic on the Courier tunneling channel. Look for patterns indicating static or reused credentials across multiple devices.Affected if Traffic analysis reveals non-unique or static TLS credentials being used for Courier communication
You are affected if you use any Schneider Electric Easergy P14x, P24x, or P34x model with Courier tunneling enabled, as all firmware versions contain hard-coded TLS credentials in that communication channel.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace all hard-coded TLS keys with properly managed cryptographic credentials using secure key management practices, and rotate any potentially exposed keys. Verify that the Courier tunneling communication channel uses dynamically generated, properly protected credentials.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22813 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data