{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12522 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12522 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12522 is a medium-severity vulnerability in Squid-Cache Squid, published on 15 Apr 2020. 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-12522 and fix it if it is affected.\n\nWhat it is: CVE-2019-12522 is a medium-severity vulnerability in Squid-Cache Squid, published on 15 Apr 2020. 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-12522 in the wild and no public exploit code.\n\nAffected product: Squid-Cache Squid. 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-12522/ (Markdown: https://insights.sbomify.com/CVE-2019-12522/index.md)","id":"CVE-2019-12522","markdown":"https://insights.sbomify.com/CVE-2019-12522/index.md","name":"CVE-2019-12522","record":{"aliases":["DEBIAN-CVE-2019-12522","GHSA-rwjf-j42w-jfr4","UBUNTU-CVE-2019-12522"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Squid proxy server","requires_auth":"low_privilege","summary":"Attackers who compromise a child process can escalate privileges to root if Squid is run as root, due to improper handling of saved UIDs.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"squid","vendor":"squid-cache"}],"cvss":{"score":4.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"An issue was discovered in Squid through 4.7. When Squid is run as root, it spawns its child processes as a lesser user, by default the user nobody. This is done via the leave_suid call. leave_suid leaves the Saved UID as 0. This makes it trivial for an attacker who has compromised the child process to escalate their privileges back to root.","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":"Privilege escalation in n/a","id":"CVE-2019-12522","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"squid-cache:squid","products":["squid-cache:squid"],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2019-12523"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-12521"},"products":["n/a"],"published":"2020-04-15","related":[{"cvss_score":10,"headline":"Squid vulnerable to information disclosure via authentication credential leakage in error handling","id":"CVE-2025-62168","kev_date_added":null,"published":"2025-10-17"},{"cvss_score":9.3,"headline":"Squid's URN Handling can lead to Buffer Overflow","id":"CVE-2025-54574","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":9.2,"headline":"Squid vulnerable to Denial of Service in ICP Request handling","id":"CVE-2026-33526","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.7,"headline":"Squid has Denial of Service in ICP Response handling","id":"CVE-2026-32748","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.6,"headline":"SQUID-2023:10 Denial of Service in HTTP Request parsing","id":"CVE-2023-50269","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.6,"headline":"Denial of Service in HTTP Message Processing in Squid","id":"CVE-2023-49285","kev_date_added":null,"published":"2023-12-04"},{"cvss_score":8.6,"headline":"Denial of Service in Helper Process management","id":"CVE-2023-49286","kev_date_added":null,"published":"2023-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-04","vendors":["n/a"]},"summary":"Attackers who compromise a child process can escalate privileges to root if Squid is run as root, due to improper handling of saved UIDs.","url":"https://insights.sbomify.com/CVE-2019-12522/"}