{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.isis.core:isis-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-42467 in the wild and no public exploit code.","fix":"Upgrade org.apache.isis.core:isis-core to 2.0.0-M8 or later.","what":"CVE-2022-42467 is a medium-severity vulnerability in Apache Isis, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-42467 and fix it if it is affected.\n\nWhat it is: CVE-2022-42467 is a medium-severity vulnerability in Apache Isis, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-42467 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.isis.core:isis-core (Maven): affected all versions; fixed in 2.0.0-M8\n- org.apache.isis.core:isis-core (Maven): affected all versions; fixed in 2.0.0-M8\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-2022-42467/ (Markdown: https://insights.sbomify.com/CVE-2022-42467/index.md)","id":"CVE-2022-42467","markdown":"https://insights.sbomify.com/CVE-2022-42467/index.md","name":"CVE-2022-42467","record":{"aliases":["GHSA-998r-j9rx-qm8m"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Isis framework","requires_auth":"none","summary":"The h2 webconsole in Apache Isis prototype mode was enabled by default, allowing direct database access; developers must now explicitly enable it via configuration.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"isis","vendor":"apache"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"When running in prototype mode, the h2 webconsole module (accessible from the Prototype menu) is automatically made available with the ability to directly query the database. It was felt that it is safer to require the developer to explicitly enable this capability. As of 2.0.0-M8, this can now be done using the 'isis.prototyping.h2-console.web-allow-remote-access' configuration property; the web console will be unavailable without setting this configuration. As an additional safeguard, the new 'isis.prototyping.h2-console.generate-random-web-admin-password' configuration parameter (enabled by default) requires that the administrator use a randomly generated password to use the console. The password is printed to the log, as \"webAdminPass: xxx\" (where \"xxx\") is the password. To revert to the original behaviour, the administrator would therefore need to set these configuration parameter: isis.prototyping.h2-console.web-allow-remote-access=true isis.prototyping.h2-console.generate-random-web-admin-password=false Note also that the h2 webconsole is never available in production mode, so these safeguards are only to ensure that the webconsole is secured by default also in prototype mode.","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":"h2 webconsole (available only in prototype mode) should nevertheless be disabled by default.","id":"CVE-2022-42467","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"misconfiguration","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Apache Flume prior to 1.11.0 has an Improper Input Validation (JNDI Injection) in JMSSource","id":"CVE-2022-42468"},"packages":[{"ecosystem":"Maven","fixed":["2.0.0-M8"],"introduced":["0"],"last_affected":[],"package":"org.apache.isis.core:isis-core","purl":null,"source":"GHSA-998r-j9rx-qm8m"},{"ecosystem":"Maven","fixed":["2.0.0-M8"],"introduced":["0"],"last_affected":[],"package":"org.apache.isis.core:isis-core","purl":"pkg:maven/org.apache.isis.core/isis-core","source":"GHSA-998r-j9rx-qm8m"}],"prev":{"headline":"XSS vulnerability, eg for String properties.","id":"CVE-2022-42466"},"products":["Apache Isis"],"published":"2022-10-19","related":[{"cvss_score":6.1,"headline":"XSS vulnerability, eg for String properties.","id":"CVE-2022-42466","kev_date_added":null,"published":"2022-10-19"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Apache Software Foundation"]},"summary":"The h2 webconsole in Apache Isis prototype mode was enabled by default, allowing direct database access; developers must now explicitly enable it via configuration.","url":"https://insights.sbomify.com/CVE-2022-42467/"}