{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-11288 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11288 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11288 is a high-severity vulnerability in Pivotal tc Server 3.x, published on 27 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-11288 and fix it if it is affected.\n\nWhat it is: CVE-2019-11288 is a high-severity vulnerability in Pivotal tc Server 3.x, published on 27 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-11288 in the wild and no public exploit code.\n\nAffected product: Pivotal tc Server 3.x. 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-2019-11288/ (Markdown: https://insights.sbomify.com/CVE-2019-11288/index.md)","id":"CVE-2019-11288","markdown":"https://insights.sbomify.com/CVE-2019-11288/index.md","name":"CVE-2019-11288","record":{"aliases":["GHSA-gfwv-ggwh-qj2r"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Pivotal tc Server","requires_auth":"low_privilege","summary":"Local attackers can hijack JMX RMI registry to steal credentials and gain full control over the tc Runtime instance.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"pivotal","cpe":[{"product":"tc_runtimes","vendor":"pivotal"},{"product":"tc_server","vendor":"pivotal"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"In Pivotal tc Server, 3.x versions prior to 3.2.19 and 4.x versions prior to 4.0.10, and Pivotal tc Runtimes, 7.x versions prior to 7.0.99.B, 8.x versions prior to 8.5.47.A, and 9.x versions prior to 9.0.27.A, when a tc Runtime instance is configured with the JMX Socket Listener, a local attacker without access to the tc Runtime process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the tc Runtime instance.","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":"tcServer JMX Socket Listener Registry Rebinding Local Privilege Escalation","id":"CVE-2019-11288","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"A forged route service request using an invalid nonce can cause the gorouter to panic and crash","id":"CVE-2019-11289"},"packages":[],"prev":{"headline":"RabbitMQ Web Management Plugin DoS via heap overflow","id":"CVE-2019-11287"},"products":["Pivotal tc Server 3.x","Pivotal tc Server 3.x Runtimes","Pivotal tc Server 4.x","Pivotal tc Server 4.x Runtimes"],"published":"2020-01-27","related":[],"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-17","vendors":["Pivotal"]},"summary":"Local attackers can hijack JMX RMI registry to steal credentials and gain full control over the tc Runtime instance.","url":"https://insights.sbomify.com/CVE-2019-11288/"}