{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1973 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1973 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1973 is a high-severity vulnerability in Ibm Api Connect, published on 20 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1973 and fix it if it is affected.\n\nWhat it is: CVE-2018-1973 is a high-severity vulnerability in Ibm Api Connect, published on 20 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1973 in the wild and no public exploit code.\n\nAffected product: Ibm Api Connect. 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-2018-1973/ (Markdown: https://insights.sbomify.com/CVE-2018-1973/index.md)","id":"CVE-2018-1973","markdown":"https://insights.sbomify.com/CVE-2018-1973/index.md","name":"CVE-2018-1973","record":{"aliases":["GHSA-xmq2-3xpw-g24h"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"API management platform","requires_auth":"high_privilege","summary":"An API Administrator can escalate privileges to full Administrator access via the members functionality in IBM API Connect.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"api_connect","vendor":"ibm"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.0/A:H/AC:L/AV:N/C:H/I:H/PR:H/S:U/UI:N/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"IBM API Connect 5.0.0.0 through 5.0.8.4 allows a user with limited 'API Administrator level access to give themselves full 'Administrator' level access through the members functionality. IBM X-Force ID: 153914.","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":"Privilege escalation in API Connect","id":"CVE-2018-1973","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:api_connect","products":["ibm:api_connect"],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in MQ","id":"CVE-2018-1974"},"packages":[],"prev":{"headline":"XML external entity in Security Identity Manager","id":"CVE-2018-1970"},"products":["API Connect"],"published":"2018-12-20","related":[{"cvss_score":10,"headline":"Command injection in API Connect","id":"CVE-2019-4202","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":9.8,"headline":"Authentication bypass in IBM API Connect","id":"CVE-2025-13915","kev_date_added":null,"published":"2025-12-26"},{"cvss_score":9.8,"headline":"Command injection in API Connect","id":"CVE-2018-1469","kev_date_added":null,"published":"2018-04-04"},{"cvss_score":9.1,"headline":"IBM API Connect SQL Injection","id":"CVE-2026-9074","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":9,"headline":"Information disclosure in API Connect","id":"CVE-2019-4008","kev_date_added":null,"published":"2019-02-07"},{"cvss_score":8.9,"headline":"Server-side request forgery in API Connect","id":"CVE-2019-4203","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":8.9,"headline":"Code injection in API Connect","id":"CVE-2018-1774","kev_date_added":null,"published":"2018-11-09"}],"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-09-16","vendors":["IBM"]},"summary":"An API Administrator can escalate privileges to full Administrator access via the members functionality in IBM API Connect.","url":"https://insights.sbomify.com/CVE-2018-1973/"}