This CPE summary could be partial or incomplete. Please contact us for a detailed listing.

Summary

Detail
Vendor Eclipse First view 2021-01-20
Product Vert.X-Web Last view 2023-02-09
Version Type Application
Update  
Edition  
Language  
Sofware Edition  
Target Software  
Target Hardware  
Other  

Activity : Overall

COMMON PLATFORM ENUMERATION: Repartition per Version

CPE Name Affected CVE
cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone1:*:*:*:*:*:* 2
cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone2:*:*:*:*:*:* 2
cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone3:*:*:*:*:*:* 2
cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone4:*:*:*:*:*:* 2
cpe:2.3:a:eclipse:vert.x-web:*:*:*:*:*:*:*:* 1

Related : CVE

  Date Alert Description
5.3 2023-02-09 CVE-2023-24815

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.

8.8 2021-01-20 CVE-2020-35217

Vert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.

CWE : Common Weakness Enumeration

%idName
50% (1) CWE-352 Cross-Site Request Forgery (CSRF)
50% (1) CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path ...