{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-5023 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5023 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5023 is a medium-severity memory corruption vulnerability in PaX, published on 31 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-5023 and fix it if it is affected.\n\nWhat it is: CVE-2019-5023 is a medium-severity memory corruption vulnerability in PaX, published on 31 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-5023 in the wild and no public exploit code.\n\nAffected product: PaX. 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-2019-5023/ (Markdown: https://insights.sbomify.com/CVE-2019-5023/index.md)","id":"CVE-2019-5023","markdown":"https://insights.sbomify.com/CVE-2019-5023/index.md","name":"CVE-2019-5023","record":{"aliases":["GHSA-vjqv-f876-5p65"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel security patch","requires_auth":"none","summary":"A memory leak in the PaX kernel patch allows attackers to crash the system by triggering a read from /dev/kmem with an invalid address.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"grsecurity","vendor":"opensrcsec"},{"product":"pax","vendor":"opensrcsec"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-772","name":"Missing Release of Resource after Effective Lifetime"},{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"An exploitable vulnerability exists in the grsecurity PaX patch for the function read_kmem, in PaX from version pax-linux-4.9.8-test1 to 4.9.24-test7, grsecurity official from version grsecurity-3.1-4.9.8-201702060653 to grsecurity-3.1-4.9.24-201704252333, grsecurity unofficial from version v4.9.25-unofficialgrsec to v4.9.74-unofficialgrsec. PaX adds a temp buffer to the read_kmem function, which is never freed when an invalid address is supplied. This results in a memory leakage that can lead to a crash of the system. An attacker needs to induce a read to /dev/kmem using an invalid address to exploit this vulnerability.","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":"Memory corruption in PaX","id":"CVE-2019-5023","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Capsule Technologies SmartLinx Neuron 2","id":"CVE-2019-5024"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-5022"},"products":["PaX"],"published":"2019-10-31","related":[],"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":"A memory leak in the PaX kernel patch allows attackers to crash the system by triggering a read from /dev/kmem with an invalid address.","url":"https://insights.sbomify.com/CVE-2019-5023/"}