{"answers":{"affected":"2 open source packages ship an affected version, including io.vertx:vertx-web. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24815 exists.","fix":"Upgrade io.vertx:vertx-web to 4.3.8 or later.","what":"CVE-2023-24815 is a medium-severity path traversal vulnerability in vert-x3 vertx-web, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-24815 and fix it if it is affected.\n\nWhat it is: CVE-2023-24815 is a medium-severity path traversal vulnerability in vert-x3 vertx-web, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24815 exists.\n\nAffected packages and fixed versions:\n- io.vertx:vertx-web (Maven): affected from 4.0.0; fixed in 4.3.8\n- io.vertx:vertx-web (Maven): affected from 4.0.0; fixed in 4.3.8\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-2023-24815/ (Markdown: https://insights.sbomify.com/CVE-2023-24815/index.md)","id":"CVE-2023-24815","markdown":"https://insights.sbomify.com/CVE-2023-24815/index.md","name":"CVE-2023-24815","record":{"aliases":["GHSA-53jx-vvf9-4x38"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Vert.x Web library","requires_auth":"none","summary":"Attackers can exfiltrate classpath resources on Windows deployments using wildcard routes due to improper path validation in Vert.x Web.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vert.x-web","vendor":"eclipse"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Vert.x-Web is a set of building blocks for building web applications in the java programming language. When running vertx web applications that serve files using `StaticHandler` on Windows Operating Systems and Windows File Systems, if the mount point is a wildcard (`*`) then an attacker can exfiltrate any class path resource. When computing the relative path to locate the resource, in case of wildcards, the code: `return \"/\" + rest;` from `Utils.java` returns the user input (without validation) as the segment to lookup. Even though checks are performed to avoid escaping the sandbox, given that the input was not sanitized `\\` are not properly handled and an attacker can build a path that is valid within the classpath. This issue only affects users deploying in windows environments and upgrading is the advised remediation path. There are no known workarounds for this vulnerability.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Disclosure of classpath resources on Windows when mounted on a wildcard route in vertx-web","id":"CVE-2023-24815","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"set_term_title command injection in ipython","id":"CVE-2023-24816"},"packages":[{"ecosystem":"Maven","fixed":["4.3.8"],"introduced":["4.0.0"],"last_affected":[],"package":"io.vertx:vertx-web","purl":null,"source":"GHSA-53jx-vvf9-4x38"},{"ecosystem":"Maven","fixed":["4.3.8"],"introduced":["4.0.0"],"last_affected":[],"package":"io.vertx:vertx-web","purl":"pkg:maven/io.vertx/vertx-web","source":"GHSA-53jx-vvf9-4x38"}],"prev":{"headline":"Persisted Cross-Site Scripting in Frontend Rendering in typo3","id":"CVE-2023-24814"},"products":["vertx-web"],"published":"2023-02-09","related":[{"cvss_score":8.8,"headline":"Cross-Site Request Forgery in Vert.x-Web framework","id":"CVE-2020-35217","kev_date_added":null,"published":"2021-01-20"},{"cvss_score":6.9,"headline":"Eclipse Vert.x Web static handler file access denial","id":"CVE-2026-1002","kev_date_added":null,"published":"2026-01-15"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["vert-x3"]},"summary":"Attackers can exfiltrate classpath resources on Windows deployments using wildcard routes due to improper path validation in Vert.x Web.","url":"https://insights.sbomify.com/CVE-2023-24815/"}