{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25479 exists.","fix":"No fix has been published for CVE-2022-25479 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25479 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-25479 and fix it if it is affected.\n\nWhat it is: CVE-2022-25479 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25479 exists.\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-25479/ (Markdown: https://insights.sbomify.com/CVE-2022-25479/index.md)","id":"CVE-2022-25479","markdown":"https://insights.sbomify.com/CVE-2022-25479/index.md","name":"CVE-2022-25479","record":{"aliases":["GHSA-7vph-xj83-rw6v"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Realtek card reader driver","requires_auth":"low_privilege","summary":"A vulnerability in Realtek card reader drivers allows attackers to leak kernel memory from the stack and heap, potentially exposing sensitive data.","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":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"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 allows for the leakage of kernel memory from both the stack and the heap.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-09-17","github_poc":1,"max_poc_stars":46,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-09-17T06:28:17Z","kind":"github_poc","ref":"https://github.com/SpiralBL0CK/CVE-2024-40431-CVE-2022-25479-EOP-CHAIN","stars":46,"title":"CVE-2024-40431+CVE-2022-25479 chain for EOP(DATA ONLY ATTACK) "}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2022-25479","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":"Memory corruption in n/a","id":"CVE-2022-25480"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2022-25478"},"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":5.5,"headline":"Information disclosure in n/a","id":"CVE-2022-25477","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"A vulnerability in Realtek card reader drivers allows attackers to leak kernel memory from the stack and heap, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2022-25479/"}