{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21250 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-21250 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21250 is a high-severity vulnerability in theonedev onedev, published on 15 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21250 and fix it if it is affected.\n\nWhat it is: CVE-2021-21250 is a high-severity vulnerability in theonedev onedev, published on 15 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-21250 in the wild and no public exploit code.\n\nAffected product: theonedev onedev. 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-2021-21250/ (Markdown: https://insights.sbomify.com/CVE-2021-21250/index.md)","id":"CVE-2021-21250","markdown":"https://insights.sbomify.com/CVE-2021-21250/index.md","name":"CVE-2021-21250","record":{"aliases":["GHSA-9pph-8gfc-6w2r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OneDev DevOps Platform","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit XML external entity injection in OneDev to read arbitrary files from the server filesystem.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"onedev","vendor":"onedev_project"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-538","name":"Insertion of Sensitive Information into Externally-Accessible File or Directory"}],"description":"OneDev is an all-in-one devops platform. In OneDev before version 4.0.3, there is a critical vulnerability which may lead to arbitrary file read. When BuildSpec is provided in XML format, the spec is processed by XmlBuildSpecMigrator.migrate(buildSpecString); which processes the XML document without preventing the expansion of external entities. These entities can be configured to read arbitrary files from the file system and dump their contents in the final XML document to be migrated. If the files are dumped in properties included in the YAML file, it will be possible for an attacker to read them. If not, it is possible for an attacker to exfiltrate the contents of these files Out Of Band. This issue was addressed in 4.0.3 by ignoring ENTITY instructions in xml file.","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":"Post-Auth External Entity Expansion (XXE)","id":"CVE-2021-21250","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"ZipSlip Arbitrary File Upload","id":"CVE-2021-21251"},"packages":[],"prev":{"headline":"Post-Auth Unsafe Yaml deserialization","id":"CVE-2021-21249"},"products":["onedev"],"published":"2021-01-15","related":[{"cvss_score":10,"headline":"Pre-Auth Unsafe Deserialization on AttachmentUploadServet","id":"CVE-2021-21242","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":10,"headline":"Pre-Auth Unsafe Deserialization on KubernetesResource","id":"CVE-2021-21243","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":10,"headline":"Pre-Auth SSTI via Bean validation message tampering","id":"CVE-2021-21244","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":10,"headline":"Pre-Auth Arbitrary File Upload","id":"CVE-2021-21245","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":9.9,"headline":"CI/CD Docker Escape in OneDev","id":"CVE-2022-39206","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":9.6,"headline":"Post-Auth Unsafe Deserialization on BasePage (AJAX)","id":"CVE-2021-21247","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":9.6,"headline":"Post-Auth Arbitrary Code execution via Groovy script injection","id":"CVE-2021-21248","kev_date_added":null,"published":"2021-01-15"}],"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-03","vendors":["theonedev"]},"summary":"Authenticated attackers can exploit XML external entity injection in OneDev to read arbitrary files from the server filesystem.","url":"https://insights.sbomify.com/CVE-2021-21250/"}