CVE-2023-48034
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 · uneditedAn issue discovered in Acer Wireless Keyboard SK-9662 allows attacker in physical proximity to both decrypt wireless keystrokes and inject arbitrary keystrokes via use of weak encryption.
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 confidenceThe Acer Wireless Keyboard SK-9662 uses weak encryption in its wireless protocol, enabling an attacker within physical proximity to intercept and decrypt keystrokes transmitted wirelessly, as well as inject arbitrary keystrokes back into the connection, effectively allowing keylogging and keystroke injection attacks.
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 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 keyboard modelPhysically examine the underside or front of your keyboard for a model number label. The Acer SK-9662 typically has a label showing 'SK-9662' or 'Acer Wireless Keyboard SK-9662'.Affected if The model number matches SK-9662 or Acer Sk 9662
-
Verify wireless connectivityConfirm the keyboard is operating wirelessly. The SK-9662 is a wireless keyboard that communicates via a USB receiver or Bluetooth. Check if a small USB dongle is plugged into the computer, indicating active wireless communication.Affected if The keyboard is connected and functioning wirelessly via its included USB receiver or Bluetooth adapter
-
Check for encrypted wireless protocolsExamine the keyboard documentation or system settings to determine what wireless encryption protocol the keyboard uses. The CVE specifically notes weak encryption in the wireless protocol. If no documentation is available, this indicates the vulnerability cannot be ruled out.Affected if The wireless protocol uses weak or undocumented encryption, or encryption details cannot be verified
-
Assess physical exposure riskDetermine the keyboard's usage environment. The vulnerability allows attacks from physical proximity, meaning anyone within wireless range could intercept or inject keystrokes.Affected if The keyboard is used in shared offices, public spaces, or any environment where untrusted individuals could be within wireless range
If the keyboard model is Acer SK-9662 or Acer Sk 9662 and it is being used wirelessly, the environment is affected by this vulnerability regardless of firmware version since all versions are impacted.
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 the affected keyboard with a wired keyboard or a wireless keyboard employing strong encryption (e.g., AES-128 or higher). Until replacement, avoid using the keyboard for sensitive inputs in public or shared spaces.
- Consultation2.0 h
- Implementation3.0 h
- Testing1.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,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48034 — 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-2023-48034 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