{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-11396 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11396 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11396 is a high-severity vulnerability in n/a, published on 29 Aug 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-11396 and fix it if it is affected.\n\nWhat it is: CVE-2019-11396 is a high-severity vulnerability in n/a, published on 29 Aug 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-11396 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-11396/ (Markdown: https://insights.sbomify.com/CVE-2019-11396/index.md)","id":"CVE-2019-11396","markdown":"https://insights.sbomify.com/CVE-2019-11396/index.md","name":"CVE-2019-11396","record":{"aliases":["GHSA-wg87-3vq4-8632"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Avira Security Suite","requires_auth":"low_privilege","summary":"Unprivileged users can escalate to SYSTEM privileges by exploiting insecure file permissions and symlink attacks in the Avira SoftwareUpdater component.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"free_security_suite","vendor":"avira"},{"product":"software_updater","vendor":"avira"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"An issue was discovered in Avira Free Security Suite 10. The permissive access rights on the SoftwareUpdater folder (files / folders and configuration) are incompatible with the privileged file manipulation performed by the product. Files can be created that can be used by an unprivileged user to obtain SYSTEM privileges. Arbitrary file creation can be achieved by abusing the SwuConfig.json file creation: an unprivileged user can replace these files by pseudo-symbolic links to arbitrary files. When an update occurs, a privileged service creates a file and sets its access rights, offering write access to the Everyone group in any directory.","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-11396","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2019-11397"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-11395"},"products":["n/a"],"published":"2019-08-29","related":[{"cvss_score":6.7,"headline":"Code injection in n/a","id":"CVE-2017-6417","kev_date_added":null,"published":"2017-03-21"}],"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 users can escalate to SYSTEM privileges by exploiting insecure file permissions and symlink attacks in the Avira SoftwareUpdater component.","url":"https://insights.sbomify.com/CVE-2019-11396/"}