{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2020-10095 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10095 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10095 is a high-severity vulnerability in n/a, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-10095 and fix it if it is affected.\n\nWhat it is: CVE-2020-10095 is a high-severity vulnerability in n/a, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-10095 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-2020-10095/ (Markdown: https://insights.sbomify.com/CVE-2020-10095/index.md)","id":"CVE-2020-10095","markdown":"https://insights.sbomify.com/CVE-2020-10095/index.md","name":"CVE-2020-10095","record":{"aliases":["GHSA-p6g2-26xx-9595"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Lexmark network device","requires_auth":"none","summary":"Attackers can modify device configuration via CSRF, affecting Lexmark network devices.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Various Lexmark devices have CSRF that allows an attacker to modify the configuration of the device.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-10095","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-10096"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-10094"},"products":["n/a"],"published":"2025-02-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-20","vendors":["n/a"]},"summary":"Attackers can modify device configuration via CSRF, affecting Lexmark network devices.","url":"https://insights.sbomify.com/CVE-2020-10095/"}