{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6480 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6480 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6480 is a high-severity memory corruption vulnerability in n/a, published on 31 Jan 2018. 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-2018-6480 and fix it if it is affected.\n\nWhat it is: CVE-2018-6480 is a high-severity memory corruption vulnerability in n/a, published on 31 Jan 2018. 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-2018-6480 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-2018-6480/ (Markdown: https://insights.sbomify.com/CVE-2018-6480/index.md)","id":"CVE-2018-6480","markdown":"https://insights.sbomify.com/CVE-2018-6480/index.md","name":"CVE-2018-6480","record":{"aliases":["GHSA-678v-754j-47w8"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"CCN-lite networking library","requires_auth":"none","summary":"A type confusion in CCN-lite causes memory access violations and nonce failures, potentially leading to denial of service.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ccn-lite","vendor":"ccn-lite"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-704","name":"Incorrect Type Conversion or Cast"}],"description":"A type confusion issue was discovered in CCN-lite 2, leading to a memory access violation and a failure of the nonce feature (which, for example, helped with loop prevention). ccnl_fwd_handleInterest assumes that the union member s is of type ccnl_pktdetail_ndntlv_s. However, if the type is in fact struct ccnl_pktdetail_ccntlv_s or struct ccnl_pktdetail_iottlv_s, the memory at that point is either uninitialised or points to data that is not a nonce, which renders the code using the local variable nonce pointless. A later nonce check is insufficient.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in n/a","id":"CVE-2018-6480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-6481"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-6479"},"products":["n/a"],"published":"2018-01-31","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-12889","kev_date_added":null,"published":"2018-06-26"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2018-7039","kev_date_added":null,"published":"2018-02-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-6948","kev_date_added":null,"published":"2018-02-13"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-6953","kev_date_added":null,"published":"2018-02-13"},{"cvss_score":9.8,"headline":"Multiple integer overflows in CCN-lite before 2.00 allow context-dependent attackers to have unspecified impact via vectors involving the (1","id":"CVE-2017-12465","kev_date_added":null,"published":"2018-02-07"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-12466","kev_date_added":null,"published":"2018-02-07"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-12468","kev_date_added":null,"published":"2018-02-07"}],"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-09-17","vendors":["n/a"]},"summary":"A type confusion in CCN-lite causes memory access violations and nonce failures, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2018-6480/"}