{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-16919 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16919 is a high-severity missing authorization vulnerability in Vmware Cloud Foundation, published on 18 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-16919 and fix it if it is affected.\n\nWhat it is: CVE-2019-16919 is a high-severity missing authorization vulnerability in Vmware Cloud Foundation, published on 18 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-16919 in the wild and no public exploit code.\n\nAffected product: Vmware Cloud Foundation. 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-16919/ (Markdown: https://insights.sbomify.com/CVE-2019-16919/index.md)","id":"CVE-2019-16919","markdown":"https://insights.sbomify.com/CVE-2019-16919/index.md","name":"CVE-2019-16919","record":{"aliases":["GHSA-gm4w-75rj-3wr6","GHSA-x2r2-w9c7-h624"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Harbor container registry","requires_auth":"none","summary":"Project administrators can create robot accounts with unauthorized access to other projects due to missing API permission checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"harbor","vendor":"linuxfoundation"},{"product":"cloud_foundation","vendor":"vmware"},{"product":"harbor_container_registry","vendor":"vmware"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"Harbor API has a Broken Access Control vulnerability. The vulnerability allows project administrators to use the Harbor API to create a robot account with unauthorized push and/or pull access permissions to a project they don't have access or control for. The Harbor API did not enforce the proper project permissions and project scope on the API request to create a new robot account.","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":"Missing authorization in n/a","id":"CVE-2019-16919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vmware:cloud_foundation","products":["vmware:cloud_foundation"],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"D-Link Multiple Routers Command Injection","id":"CVE-2019-16920"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2019-16917"},"products":["n/a"],"published":"2019-10-18","related":[{"cvss_score":9.4,"headline":"Use of hard coded credentials in GoHarbor Harbor","id":"CVE-2026-4404","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.8,"headline":"Privilege Escalation in Cloud Native Computing Foundation Harbor","id":"CVE-2019-19023","kev_date_added":null,"published":"2020-03-20"},{"cvss_score":8.8,"headline":"Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation Harbor","id":"CVE-2019-19025","kev_date_added":null,"published":"2020-03-20"},{"cvss_score":8.6,"headline":"Server-side request forgery in n/a","id":"CVE-2017-17697","kev_date_added":null,"published":"2017-12-15"},{"cvss_score":7.7,"headline":"Harbor fails to validate user permissions while Viewing, updating and deleting Webhook policies","id":"CVE-2022-31666","kev_date_added":null,"published":"2024-11-14"},{"cvss_score":7.7,"headline":"Harbor fails to validate the user permissions when updating tag retention policies","id":"CVE-2022-31670","kev_date_added":null,"published":"2024-11-14"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2022-46463","kev_date_added":null,"published":"2023-01-12"}],"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-05","vendors":["n/a"]},"summary":"Project administrators can create robot accounts with unauthorized access to other projects due to missing API permission checks.","url":"https://insights.sbomify.com/CVE-2019-16919/"}