{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3699 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3699 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3699 is a high-severity vulnerability in openSUSE Factory, published on 24 Jan 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-3699 and fix it if it is affected.\n\nWhat it is: CVE-2019-3699 is a high-severity vulnerability in openSUSE Factory, published on 24 Jan 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-3699 in the wild and no public exploit code.\n\nAffected product: openSUSE Factory. 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-3699/ (Markdown: https://insights.sbomify.com/CVE-2019-3699/index.md)","id":"CVE-2019-3699","markdown":"https://insights.sbomify.com/CVE-2019-3699/index.md","name":"CVE-2019-3699","record":{"aliases":["GHSA-j9ww-72pm-37h3"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"openSUSE Linux","requires_auth":"none","summary":"Local attackers can escalate privileges from the privoxy user to root via symlink following in openSUSE packaging.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[{"product":"privoxy","vendor":"privoxy"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"UNIX Symbolic Link (Symlink) Following vulnerability in the packaging of privoxy on openSUSE Leap 15.1, Factory allows local attackers to escalate from user privoxy to root. This issue affects: openSUSE Leap 15.1 privoxy version 3.0.28-lp151.1.1 and prior versions. openSUSE Factory privoxy version 3.0.28-2.1 and prior versions.","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":"Local privilege escalation from user privoxy to root","id":"CVE-2019-3699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"yast: Fallback to DES without configuration in /etc/login.def","id":"CVE-2019-3700"},"packages":[],"prev":{"headline":"nagios cron job allows privilege escalation from user nagios to root","id":"CVE-2019-3698"},"products":["Factory","Leap 15.1"],"published":"2020-01-24","related":[{"cvss_score":7.5,"headline":"Denial of service in Privoxy","id":"CVE-2021-44540","kev_date_added":null,"published":"2021-12-23"},{"cvss_score":7.5,"headline":"Denial of service in Privoxy","id":"CVE-2021-44541","kev_date_added":null,"published":"2021-12-23"},{"cvss_score":7.5,"headline":"Denial of service in Privoxy","id":"CVE-2021-44542","kev_date_added":null,"published":"2021-12-23"},{"cvss_score":7.5,"headline":"Denial of service in privoxy","id":"CVE-2021-20209","kev_date_added":null,"published":"2021-05-25"},{"cvss_score":7.5,"headline":"Denial of service in privoxy","id":"CVE-2020-35502","kev_date_added":null,"published":"2021-03-25"},{"cvss_score":7.5,"headline":"Denial of service in privoxy","id":"CVE-2021-20210","kev_date_added":null,"published":"2021-03-25"}],"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-16","vendors":["openSUSE"]},"summary":"Local attackers can escalate privileges from the privoxy user to root via symlink following in openSUSE packaging.","url":"https://insights.sbomify.com/CVE-2019-3699/"}