CVE-2022-45480
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 · uneditedPC Keyboard WiFi & Bluetooth allows an attacker (in a man-in-the-middle position between the server and a connected device) to see all data (including keypresses) in cleartext. CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 · high confidenceThe PC Keyboard WiFi & Bluetooth application transmits all data including keypresses in cleartext without encryption. An attacker positioned as a man-in-the-middle between the server and connected device can intercept and read sensitive keystroke data in plaintext.
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<= 30CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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 installed version of the PC Keyboard appOn Android: Go to Settings > Apps > PC Keyboard WiFi & Bluetooth, then check the Version or Version Code field. On iOS: Go to Settings > General > iPhone Storage, find the app, and check the version number.Affected if The displayed version number is 30 or lower (any version <= 30).
-
Verify if the app transmits keypress data over encrypted channelsUse a network capture tool (such as Wireshark, tcpdump, or a mobile proxy) to intercept network traffic while typing with the app. Examine the captured packets for plaintext keypress data being sent to the server.Affected if Network traffic shows unencrypted keypress data transmitted in plaintext (no TLS/SSL wrapper visible in the captured packets).
-
Confirm the communication protocol used by the appInspect the captured network traffic for the protocol in use. Look for cleartext HTTP connections rather than HTTPS, or non-encrypted socket connections.Affected if The app communicates using unencrypted protocols (HTTP on port 80, unencrypted TCP sockets, or similar cleartext protocols) instead of TLS/SSL-wrapped connections.
Your environment is affected if you have version 30 or lower of the Beappsmobile PC Keyboard WiFi & Bluetooth app installed AND network traffic analysis reveals cleartext transmission of keystroke data without encryption.
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 dataImplement encrypted communication protocols (e.g., TLS/SSL or equivalent encryption) for all data transmission between the server and connected devices to protect confidentiality of keypresses and other sensitive data.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45480 — 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-45480 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