{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-5508 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-5508 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-5508 is a medium-severity denial of service vulnerability in F5 Big-Ip Policy Enforcement Manager, published on 13 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-5508 and fix it if it is affected.\n\nWhat it is: CVE-2018-5508 is a medium-severity denial of service vulnerability in F5 Big-Ip Policy Enforcement Manager, published on 13 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-5508 in the wild and no public exploit code.\n\nAffected product: F5 Big-Ip Policy Enforcement Manager. 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-5508/ (Markdown: https://insights.sbomify.com/CVE-2018-5508/index.md)","id":"CVE-2018-5508","markdown":"https://insights.sbomify.com/CVE-2018-5508/index.md","name":"CVE-2018-5508","record":{"aliases":["GHSA-8pm9-x397-wxmf"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"F5 BIG-IP PEM","requires_auth":"none","summary":"Attackers can crash the Traffic Management Microkernel by sending compressed data through a Virtual Server with specific PEM profile settings.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"f5","cpe":[{"product":"big-ip_policy_enforcement_manager","vendor":"f5"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[],"description":"On F5 BIG-IP PEM versions 13.0.0, 12.0.0-12.1.3.1, 11.6.0-11.6.2, 11.5.1-11.5.5, or 11.2.1, under certain conditions, TMM may crash when processing compressed data though a Virtual Server with an associated PEM profile using the content insertion option.","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":"Denial of service in BIG-IP (PEM)","id":"CVE-2018-5508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"f5:big-ip_policy_enforcement_manager","products":["f5:big-ip_policy_enforcement_manager"],"type":"denial_of_service","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in BIG-IP (LTM, AAM, AFM, APM, ASM, Link Controller, PEM, WebSafe)","id":"CVE-2018-5509"},"packages":[],"prev":{"headline":"Other in BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, GTM, Link Controller, PEM, WebAccelerator, WebSafe)","id":"CVE-2018-5507"},"products":["BIG-IP (PEM)"],"published":"2018-04-13","related":[{"cvss_score":8.7,"headline":"BIG-IP PEM vulnerability","id":"CVE-2025-35995","kev_date_added":null,"published":"2025-05-07"},{"cvss_score":8.7,"headline":"BIG-IP PEM Vulnerability","id":"CVE-2025-22891","kev_date_added":null,"published":"2025-02-05"},{"cvss_score":8.7,"headline":"BIG-IP PEM vulnerability","id":"CVE-2025-24497","kev_date_added":null,"published":"2025-02-05"},{"cvss_score":7.5,"headline":"BIG-IP PEM vulnerability","id":"CVE-2024-23982","kev_date_added":null,"published":"2024-02-14"},{"cvss_score":7.5,"headline":"Denial of service in BIG-IP (PEM)","id":"CVE-2020-5942","kev_date_added":null,"published":"2020-11-05"},{"cvss_score":7.5,"headline":"Denial of service in BIG-IP PEM","id":"CVE-2019-6628","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":7.5,"headline":"Denial of service in BIG-IP (PEM)","id":"CVE-2018-5503","kev_date_added":null,"published":"2018-03-22"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["F5 Networks, Inc."]},"summary":"Attackers can crash the Traffic Management Microkernel by sending compressed data through a Virtual Server with specific PEM profile settings.","url":"https://insights.sbomify.com/CVE-2018-5508/"}