{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-7319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-7319 is a high-severity vulnerability in n/a, published on 26 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-7319 and fix it if it is affected.\n\nWhat it is: CVE-2019-7319 is a high-severity vulnerability in n/a, published on 26 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-7319 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-7319/ (Markdown: https://insights.sbomify.com/CVE-2019-7319/index.md)","id":"CVE-2019-7319","markdown":"https://insights.sbomify.com/CVE-2019-7319/index.md","name":"CVE-2019-7319","record":{"aliases":["GHSA-g479-c966-m99h"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Cloudera Hue","requires_auth":"low_privilege","summary":"External users gain superuser privileges when specific authentication backends are enabled in Cloudera Hue.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cdh","vendor":"cloudera"}],"cvss":{"score":8.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"An issue was discovered in Cloudera Hue 6.0.0 through 6.1.0. When using one of following authentication backends: LdapBackend, PamBackend, SpnegoDjangoBackend, RemoteUserDjangoBackend, SAML2Backend, OpenIDBackend, or OAuthBackend, external users are created with superuser privileges.","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-7319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-7321"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2019-7317"},"products":["n/a"],"published":"2019-11-26","related":[{"cvss_score":8.8,"headline":"In Cloudera Hue, there is privilege escalation by a read-only user when CDH 5.x brefore 5.4.9 is used.","id":"CVE-2015-7831","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2016-4572","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2016-5724","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2017-9325","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2016-6605","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":7.2,"headline":"Missing authorization in n/a","id":"CVE-2018-17860","kev_date_added":null,"published":"2019-11-26"}],"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":"External users gain superuser privileges when specific authentication backends are enabled in Cloudera Hue.","url":"https://insights.sbomify.com/CVE-2019-7319/"}