{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7656 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-7656 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-7656 is a high-severity vulnerability in n/a, published on 29 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-7656 and fix it if it is affected.\n\nWhat it is: CVE-2019-7656 is a high-severity vulnerability in n/a, published on 29 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-7656 in the wild and no public exploit code.\n\nAffected product: n/a. 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-7656/ (Markdown: https://insights.sbomify.com/CVE-2019-7656/index.md)","id":"CVE-2019-7656","markdown":"https://insights.sbomify.com/CVE-2019-7656/index.md","name":"CVE-2019-7656","record":{"aliases":["GHSA-6pq8-9hcx-5r62"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Wowza Streaming Engine","requires_auth":"low_privilege","summary":"Unprivileged Linux users can escalate to root by modifying core program files with relaxed permissions in Wowza Streaming Engine.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"streaming_engine","vendor":"wowza"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"A privilege escalation vulnerability in Wowza Streaming Engine 4.8.0 and earlier allows any unprivileged Linux user to escalate privileges to root. The installer sets too relaxed permissions on /usr/local/WowzaStreamingEngine/bin/* core program files. By injecting a payload into one of those files, it will run with the same privileges as the Wowza server, root. For example, /usr/local/WowzaStreamingEngine/bin/tune.sh could be replaced with a Trojan horse. This issue was resolved in Wowza Streaming Engine 4.8.5.","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":"Privilege escalation in n/a","id":"CVE-2019-7656","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-7659"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-7655"},"products":["n/a"],"published":"2020-01-29","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-7047","kev_date_added":null,"published":"2018-03-01"},{"cvss_score":9.4,"headline":"Stream Target Remote Code Execution in Wowza Streaming Engine","id":"CVE-2024-52052","kev_date_added":null,"published":"2024-11-21"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2018-19365","kev_date_added":null,"published":"2019-03-18"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2020-9004","kev_date_added":null,"published":"2020-04-14"},{"cvss_score":8.7,"headline":"Wowza Streaming Engine 4.5.0 Privilege Escalation via user edit","id":"CVE-2016-20034","kev_date_added":null,"published":"2026-03-15"},{"cvss_score":8.7,"headline":"Stored Cross-Site Scripting in Wowza Streaming Engine","id":"CVE-2024-52053","kev_date_added":null,"published":"2024-11-21"},{"cvss_score":8.5,"headline":"Wowza Streaming Engine 4.5.0 Local Privilege Escalation via nssm_x64.exe","id":"CVE-2016-20033","kev_date_added":null,"published":"2026-03-15"}],"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":"Unprivileged Linux users can escalate to root by modifying core program files with relaxed permissions in Wowza Streaming Engine.","url":"https://insights.sbomify.com/CVE-2019-7656/"}