{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11682 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11682 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11682 is a medium-severity vulnerability in n/a, published on 4 Jun 2020. 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-11682 and fix it if it is affected.\n\nWhat it is: CVE-2020-11682 is a medium-severity vulnerability in n/a, published on 4 Jun 2020. 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-11682 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-11682/ (Markdown: https://insights.sbomify.com/CVE-2020-11682/index.md)","id":"CVE-2020-11682","markdown":"https://insights.sbomify.com/CVE-2020-11682/index.md","name":"CVE-2020-11682","record":{"aliases":["GHSA-gxxf-h2fp-mgxp"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"DVR system","requires_auth":"none","summary":"Attackers can perform state-changing actions on Castel NextGen DVR devices by bypassing CSRF token verification, potentially altering device settings.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nextgen_dvr_firmware","vendor":"castel"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Castel NextGen DVR v1.0.0 is vulnerable to CSRF in all state-changing request. A __RequestVerificationToken is set by the web interface, and included in requests sent by web interface. However, this token is not verified by the application: the token can be removed from all requests and the request will succeed.","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-11682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-11683"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-11681"},"products":["n/a"],"published":"2020-06-04","related":[{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2020-11679","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2020-11681","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2020-11680","kev_date_added":null,"published":"2020-06-04"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can perform state-changing actions on Castel NextGen DVR devices by bypassing CSRF token verification, potentially altering device settings.","url":"https://insights.sbomify.com/CVE-2020-11682/"}