{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-4603 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-4603 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-4603 is a medium-severity vulnerability in n/a, published on 29 Dec 2010. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-4603 and fix it if it is affected.\n\nWhat it is: CVE-2010-4603 is a medium-severity vulnerability in n/a, published on 29 Dec 2010. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2010-4603 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-2010-4603/ (Markdown: https://insights.sbomify.com/CVE-2010-4603/index.md)","id":"CVE-2010-4603","markdown":"https://insights.sbomify.com/CVE-2010-4603/index.md","name":"CVE-2010-4603","record":{"aliases":["GHSA-rfr5-hrq9-32mj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Rational ClearQuest","requires_auth":"low_privilege","summary":"Authenticated users can modify back-reference fields to disrupt record relationships, potentially causing denial of service or data integrity issues.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rational_clearquest","vendor":"ibm"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"IBM Rational ClearQuest 7.0.x before 7.0.1.11, 7.1.1.x before 7.1.1.4, and 7.1.2.x before 7.1.2.1 does not prevent modification of back-reference fields, which allows remote authenticated users to interfere with intended record relationships, and possibly cause a denial of service (loop) or have unspecified other impact, by (1) adding or (2) removing a back reference.","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":"Business logic in n/a","id":"CVE-2010-4603","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2010"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2010-4604"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2010-4602"},"products":["n/a"],"published":"2010-12-29","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2010-4601","kev_date_added":null,"published":"2010-12-29"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2012-0708","kev_date_added":null,"published":"2012-04-22"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-1390","kev_date_added":null,"published":"2012-05-14"},{"cvss_score":7.5,"headline":"Multiple unspecified vulnerabilities in IBM Rational ClearQuest before 7.1.1.02 have unknown impact and attack vectors, as demonstrated by an AppScan report.","id":"CVE-2010-2517","kev_date_added":null,"published":"2010-06-30"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2008-5329","kev_date_added":null,"published":"2008-12-05"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2007-5090","kev_date_added":null,"published":"2007-09-26"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-4368","kev_date_added":null,"published":"2007-08-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Authenticated users can modify back-reference fields to disrupt record relationships, potentially causing denial of service or data integrity issues.","url":"https://insights.sbomify.com/CVE-2010-4603/"}