{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.karaf:apache-karaf. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11786 in the wild and no public exploit code.","fix":"Upgrade org.apache.karaf:apache-karaf to 4.2.0 or later.","what":"CVE-2018-11786 is a high-severity vulnerability in Apache Karaf, published on 18 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11786 and fix it if it is affected.\n\nWhat it is: CVE-2018-11786 is a high-severity vulnerability in Apache Karaf, published on 18 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-11786 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.karaf:apache-karaf (Maven): affected all versions; fixed in 4.2.0\n- org.apache.karaf:apache-karaf (Maven): affected all versions; fixed in 4.2.0\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-11786/ (Markdown: https://insights.sbomify.com/CVE-2018-11786/index.md)","id":"CVE-2018-11786","markdown":"https://insights.sbomify.com/CVE-2018-11786/index.md","name":"CVE-2018-11786","record":{"aliases":["GHSA-9448-c9wq-jg9v"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Karaf","requires_auth":"low_privilege","summary":"Users with Karaf console access can read and write arbitrary files on the host filesystem if the SSH service is enabled without strict chroot or security manager policies.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"karaf","vendor":"apache"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"In Apache Karaf prior to 4.2.0 release, if the sshd service in Karaf is left on so an administrator can manage the running instance, any user with rights to the Karaf console can pivot and read/write any file on the file system to which the Karaf process user has access. This can be locked down a bit by using chroot to change the root directory to protect files outside of the Karaf install directory; it can be further locked down by defining a security manager policy that limits file system access to those directories beneath the Karaf home that are necessary for the system to run. However, this still allows anyone with ssh access to the Karaf process to read and write a large number of files as the Karaf process user.","ecosystems":["Maven"],"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":"Improper Privilege Management in Apache Karaf","id":"CVE-2018-11786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":2,"n_references":3,"next":{"headline":"Improper Authentication in Apache Karaf","id":"CVE-2018-11787"},"packages":[{"ecosystem":"Maven","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.karaf:apache-karaf","purl":null,"source":"GHSA-9448-c9wq-jg9v"},{"ecosystem":"Maven","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.karaf:apache-karaf","purl":"pkg:maven/org.apache.karaf/apache-karaf","source":"GHSA-9448-c9wq-jg9v"}],"prev":{"headline":"Missing authorization in Apache Impala","id":"CVE-2018-11785"},"products":["Apache Karaf"],"published":"2018-09-18","related":[{"cvss_score":9.8,"headline":"Apache Karaf: Path Traversal in Config Service Allows Manager-to-Admin Privilege Escalation","id":"CVE-2026-91012","kev_date_added":null,"published":"2026-09-29"},{"cvss_score":9.8,"headline":"Missing authorization in Apache Karaf","id":"CVE-2026-91048","kev_date_added":null,"published":"2026-09-29"},{"cvss_score":9.8,"headline":"Apache Karaf: JDBC JAAS LDAP injection","id":"CVE-2022-40145","kev_date_added":null,"published":"2022-12-21"},{"cvss_score":9.8,"headline":"XML External Entity Reference in Apache Karaf","id":"CVE-2018-11788","kev_date_added":null,"published":"2019-01-07"},{"cvss_score":8.8,"headline":"Apache Karaf: Authorization bypass in JMX MBean lifecycle operations","id":"CVE-2026-92142","kev_date_added":null,"published":"2026-09-29"},{"cvss_score":8.8,"headline":"Apache Karaf: OS Command Injection in Child-Instance Launch (instance:* / InstancesMBean)","id":"CVE-2026-91006","kev_date_added":null,"published":"2026-09-28"}],"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":"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":["Apache Software Foundation"]},"summary":"Users with Karaf console access can read and write arbitrary files on the host filesystem if the SSH service is enabled without strict chroot or security manager policies.","url":"https://insights.sbomify.com/CVE-2018-11786/"}