{"answers":{"affected":"2 open source packages ship an affected version, including code.gitea.io/gitea. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1000002 in the wild and no public exploit code.","fix":"Upgrade code.gitea.io/gitea to 1.6.3 or later.","what":"CVE-2019-1000002 is a medium-severity missing authorization vulnerability in Gitea Gitea, 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-1000002 and fix it if it is affected.\n\nWhat it is: CVE-2019-1000002 is a medium-severity missing authorization vulnerability in Gitea Gitea, 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-1000002 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.6.3\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.6.3\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-1000002/ (Markdown: https://insights.sbomify.com/CVE-2019-1000002/index.md)","id":"CVE-2019-1000002","markdown":"https://insights.sbomify.com/CVE-2019-1000002/index.md","name":"CVE-2019-1000002","record":{"aliases":["GHSA-j99q-rwp6-498g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Gitea Git hosting","requires_auth":"low_privilege","summary":"An attacker with write access to any repository can delete files outside their authorized scope due to incorrect access control checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gitea","vendor":"gitea"}],"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":"Gitea version 1.6.2 and earlier contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the attacker deleting files outside the repository he/she has access to. This attack appears to be exploitable via the attacker must get write access to \"any\" repository including self-created ones.. This vulnerability appears to have been fixed in 1.6.3, 1.7.0-rc2.","ecosystems":["Go"],"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":"Gitea Arbitrary File Delete Vulnerability","id":"CVE-2019-1000002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":"gitea:gitea","products":["gitea:gitea"],"type":"missing_authorization","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-1000003"},"packages":[{"ecosystem":"Go","fixed":["1.6.3"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":null,"source":"GHSA-j99q-rwp6-498g"},{"ecosystem":"Go","fixed":["1.6.3"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GHSA-j99q-rwp6-498g"}],"prev":{"headline":"TeamPass Storing Passwords in a Recoverable Format vulnerability","id":"CVE-2019-1000001"},"products":["n/a"],"published":"2019-02-04","related":[{"cvss_score":9.8,"headline":"Gitea Code Injection","id":"CVE-2026-60004","kev_date_added":"2026-08-25","published":"2026-08-26"},{"cvss_score":9.8,"headline":"Gitea WebAuthn bypass during OAuth and OIDC sign-in","id":"CVE-2026-73278","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Gitea fork workflow approval bypass through maintainer-triggered events","id":"CVE-2026-94205","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Gitea vulnerable to Argument Injection","id":"CVE-2022-42968","kev_date_added":null,"published":"2022-10-16"},{"cvss_score":9.8,"headline":"Improper Privilege Management in Gitea","id":"CVE-2021-45330","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":9.8,"headline":"Reuse of one time passwords allowed in Gitea","id":"CVE-2021-45331","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":9.8,"headline":"Capture-replay in Gitea","id":"CVE-2021-45327","kev_date_added":null,"published":"2022-02-08"}],"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 attacker with write access to any repository can delete files outside their authorized scope due to incorrect access control checks.","url":"https://insights.sbomify.com/CVE-2019-1000002/"}