{"answers":{"affected":"4 open source packages ship an affected version, including api-platform/core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1000011 in the wild and no public exploit code.","fix":"Upgrade api-platform/core to a fixed version for your release line: 2.2.10 or 2.3.6.","what":"CVE-2019-1000011 is a medium-severity missing authorization vulnerability in n/a, published on 4 Feb 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-1000011 and fix it if it is affected.\n\nWhat it is: CVE-2019-1000011 is a medium-severity missing authorization vulnerability in n/a, published on 4 Feb 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-1000011 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- api-platform/core (Packagist): affected from 2.2.0; fixed in 2.2.10\n- api-platform/core (Packagist): affected from 2.2.0; fixed in 2.2.10\n- api-platform/core (Packagist): affected from 2.3.0; fixed in 2.3.6\n- api-platform/core (Packagist): affected from 2.3.0; fixed in 2.3.6\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-1000011/ (Markdown: https://insights.sbomify.com/CVE-2019-1000011/index.md)","id":"CVE-2019-1000011","markdown":"https://insights.sbomify.com/CVE-2019-1000011/index.md","name":"CVE-2019-1000011","record":{"aliases":["GHSA-974j-wjxx-wggj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"API Platform library","requires_auth":"low_privilege","summary":"An authenticated user can delete any resource via GraphQL mutations due to incorrect access control checks in API Platform.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"core","vendor":"api-platform"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"API Platform version from 2.2.0 to 2.3.5 contains an Incorrect Access Control vulnerability in GraphQL delete mutations that can result in a user authorized to delete a resource can delete any resource. This attack appears to be exploitable via the user must be authorized. This vulnerability appears to have been fixed in 2.3.6.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Incorrect Access Control vulnerability in api-platform/core","id":"CVE-2019-1000011","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":4,"n_references":2,"next":{"headline":"Supply chain in n/a","id":"CVE-2019-1000012"},"packages":[{"ecosystem":"Packagist","fixed":["2.2.10"],"introduced":["2.2.0"],"last_affected":[],"package":"api-platform/core","purl":null,"source":"GHSA-974j-wjxx-wggj"},{"ecosystem":"Packagist","fixed":["2.2.10"],"introduced":["2.2.0"],"last_affected":[],"package":"api-platform/core","purl":"pkg:composer/api-platform/core","source":"GHSA-974j-wjxx-wggj"},{"ecosystem":"Packagist","fixed":["2.3.6"],"introduced":["2.3.0"],"last_affected":[],"package":"api-platform/core","purl":null,"source":"GHSA-974j-wjxx-wggj"},{"ecosystem":"Packagist","fixed":["2.3.6"],"introduced":["2.3.0"],"last_affected":[],"package":"api-platform/core","purl":"pkg:composer/api-platform/core","source":"GHSA-974j-wjxx-wggj"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-1000010"},"products":["n/a"],"published":"2019-02-04","related":[{"cvss_score":7.7,"headline":"Secured properties in API Platform Core may be accessible within collections","id":"CVE-2023-25575","kev_date_added":null,"published":"2023-02-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"An authenticated user can delete any resource via GraphQL mutations due to incorrect access control checks in API Platform.","url":"https://insights.sbomify.com/CVE-2019-1000011/"}