Security readout for executives and security teams
Plain-English summary
Realtek card reader drivers can write logs containing Windows kernel memory addresses. This weakens a key operating system defense called KASLR. By itself, this is not remote code execution, but it can make another local attack more reliable. Systems with older Realtek RtsPer.sys or RtsUer.sys drivers should be updated.
Executive priority
Treat as a normal endpoint driver update priority, not an emergency. Raise priority where many users share Windows systems or where local privilege escalation risk is already a concern.
Technical view
CVE-2022-25477 is CWE-532: insertion of sensitive information into log files. Realtek RtsPer.sys before 10.0.22000.21355 and RtsUer.sys before 10.0.22000.31274 may leak kernel-mode object addresses, reducing KASLR effectiveness. CVSS 3.1 is 5.5: local attack, low complexity, low privileges, no user interaction, confidentiality impact only.
Likely exposure
Windows endpoints or devices using Realtek PCIe Card Reader RtsPer.sys or USB Card Reader RtsUer.sys drivers below the fixed versions. Exposure depends on installed hardware and OEM driver packages.
Exploitation context
The CVE record does not indicate CISA KEV listing, and the provided sources do not prove active exploitation. Abuse requires local low-privileged access and is most relevant as part of an exploit chain needing kernel address disclosure.
Researcher notes
The vulnerability is an information disclosure that weakens KASLR, not a standalone privilege escalation in the provided description. The public researcher links may provide analysis; avoid assuming broader impact beyond the named Realtek drivers and versions.
Mitigation direction
- Update RtsPer.sys to 10.0.22000.21355 or later where applicable.
- Update RtsUer.sys to 10.0.22000.31274 or later where applicable.
- Check Realtek and OEM driver guidance for supported packages.
- Prioritize shared endpoints and systems allowing untrusted local users.
Validation and detection
- Inventory Windows systems for RtsPer.sys and RtsUer.sys.
- Compare installed driver versions against the fixed versions.
- Confirm driver updates came from Realtek, Microsoft, or the OEM.
- Review vendor advisory details for any environment-specific notes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-25477 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.realtek.com/images/safe-report/Realtek_RtsPer_RtsUer_Security_Advisory_Report.pdfCVE reference, mitre
- https://gist.github.com/zwclose/feb16f1424779a61cb1d9f6d5681408aCVE reference, mitre
- https://zwclose.github.io/2024/10/14/rtsper1.htmlCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.