CVE-2022-45877
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 · uneditedOpenHarmony-v3.1.4 and prior versions had an vulnerability. PIN code is transmitted to the peer device in plain text during cross-device authentication, which reduces the difficulty of man-in-the-middle attacks.
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 confidenceIn OpenHarmony v3.1.4 and prior versions, the PIN code used for cross-device authentication is transmitted in plain text to the peer device. This allows an attacker positioned on the network path to easily intercept the PIN, significantly reducing the complexity of executing a man-in-the-middle attack against the authentication process.
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 data>= 3.1, <= 3.1.4CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify the OpenHarmony versionCheck the system version information in the device settings or using the 'getprop' command to retrieve the OpenHarmony version numberAffected if The installed version is 3.1, 3.1.1, 3.1.2, 3.1.3, or 3.1.4 (versions >= 3.1 and <= 3.1.4)
-
Determine if cross-device authentication is in useCheck if the device has peer device pairing enabled or has recent cross-device authentication events in the system logsAffected if Cross-device or peer-to-peer authentication features are actively used on the device
-
Inspect network traffic during authenticationUse a network capture tool to monitor traffic between devices during the PIN-based cross-device pairing processAffected if Network captures show the PIN code transmitted in clear, unencrypted text during the authentication handshake
The environment is affected if the installed OpenHarmony version is between 3.1 and 3.1.4 inclusive AND cross-device PIN-based authentication is being performed on the network.
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.
dbcve · scopedImplement encrypted transmission of the PIN code during cross-device authentication using a secure channel or cryptographic protocol before exchanging sensitive authentication credentials.
OpenHarmony 3.1.5 or later LTS release (e.g., 3.2.x)
- 1. Identify all devices running OpenHarmony versions 3.1 through 3.1.4 that perform cross-device authentication
- 2. Update these devices to OpenHarmony 3.1.5 or later, which contains the fix for the plain text PIN transmission vulnerability
- 3. After upgrading, verify that cross-device authentication now uses encrypted communication for PIN exchange
- 4. Test the authentication workflow to ensure proper functionality post-upgrade
- 5. Monitor for any additional security updates from the OpenHarmony project
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45877 — 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-45877 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