{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-25477 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25477 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25477 is a medium-severity vulnerability in n/a, published on 2 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-25477 and fix it if it is affected.\n\nWhat it is: CVE-2022-25477 is a medium-severity vulnerability in n/a, published on 2 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-25477 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-25477/ (Markdown: https://insights.sbomify.com/CVE-2022-25477/index.md)","id":"CVE-2022-25477","markdown":"https://insights.sbomify.com/CVE-2022-25477/index.md","name":"CVE-2022-25477","record":{"aliases":["GHSA-26wc-mjpc-3f8m"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Realtek card reader driver","requires_auth":"low_privilege","summary":"Realtek card reader drivers leak kernel object addresses in logs, weakening KASLR and aiding privilege escalation attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rtsper","vendor":"realtek"},{"product":"rtsuer","vendor":"realtek"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Vulnerability in Realtek RtsPer driver for PCIe Card Reader (RtsPer.sys) before 10.0.22000.21355 and Realtek RtsUer driver for USB Card Reader (RtsUer.sys) before 10.0.22000.31274 leaks driver logs that contain addresses of kernel mode objects, weakening KASLR.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-07-16","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-16T04:46:13Z","kind":"github_poc","ref":"https://github.com/HORKimhab/CVE-2022-25477","stars":0,"title":"CVE Realtek SD card reader. CVE-2022-25477, CVE-2022-25478, CVE-2022-25479, CVE-2022-25480, CVE-2024-40432, CVE-2024-40431"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2022-25477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2022-25478"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-25471"},"products":["n/a"],"published":"2024-07-02","related":[{"cvss_score":7.8,"headline":"Security feature bypass in n/a","id":"CVE-2022-25478","kev_date_added":null,"published":"2024-07-02"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2022-25480","kev_date_added":null,"published":"2024-07-02"},{"cvss_score":6.1,"headline":"Information disclosure in n/a","id":"CVE-2022-25479","kev_date_added":null,"published":"2024-07-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"Realtek card reader drivers leak kernel object addresses in logs, weakening KASLR and aiding privilege escalation attacks.","url":"https://insights.sbomify.com/CVE-2022-25477/"}