{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18827 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18827 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18827 is a medium-severity memory corruption vulnerability in Libav Libav, published on 30 Oct 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-18827 and fix it if it is affected.\n\nWhat it is: CVE-2018-18827 is a medium-severity memory corruption vulnerability in Libav Libav, published on 30 Oct 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-18827 in the wild and no public exploit code.\n\nAffected product: Libav Libav. 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-18827/ (Markdown: https://insights.sbomify.com/CVE-2018-18827/index.md)","id":"CVE-2018-18827","markdown":"https://insights.sbomify.com/CVE-2018-18827/index.md","name":"CVE-2018-18827","record":{"aliases":["GHSA-x55x-fv3c-r279","UBUNTU-CVE-2018-18827"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Libav media library","requires_auth":"none","summary":"Attackers can cause a denial of service in Libav by triggering a heap-based buffer over-read via a crafted AAC file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libav","vendor":"libav"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"There exists a heap-based buffer over-read in ff_vc1_pred_dc in vc1_block.c in Libav 12.3, which allows attackers to cause a denial-of-service via a crafted aac file.","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-18827","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libav:libav","products":["libav:libav"],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-18828"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-18826"},"products":["n/a"],"published":"2018-10-30","related":[{"cvss_score":10,"headline":"Multiple unspecified vulnerabilities in Libav before 0.8.12 allow remote attackers to have unknown impact and vectors.","id":"CVE-2014-3984","kev_date_added":null,"published":"2014-06-06"},{"cvss_score":9.8,"headline":"Null dereference in n/a","id":"CVE-2017-9051","kev_date_added":null,"published":"2017-05-18"},{"cvss_score":8.8,"headline":"Integer overflow in n/a","id":"CVE-2014-4609","kev_date_added":null,"published":"2020-01-14"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2019-9719","kev_date_added":null,"published":"2019-09-19"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-5766","kev_date_added":null,"published":"2018-01-18"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-5684","kev_date_added":null,"published":"2018-01-14"},{"cvss_score":8.8,"headline":"Null dereference in n/a","id":"CVE-2017-17129","kev_date_added":null,"published":"2017-12-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-05","vendors":["n/a"]},"summary":"Attackers can cause a denial of service in Libav by triggering a heap-based buffer over-read via a crafted AAC file.","url":"https://insights.sbomify.com/CVE-2018-18827/"}