GHSA-9Q69-G5GC-9FGF
Vulnerability from github – Published: 2021-04-22 16:16 – Updated: 2021-04-20 17:07
VLAI?
Summary
Cross-Site Request Forgery in Vert.x-Web framework
Details
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.
Severity ?
8.8 (High)
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "io.vertx:vertx-web"
},
"ranges": [
{
"events": [
{
"introduced": "4.0.0-milestone1"
},
{
"fixed": "4.0.0-milestone5"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.0.0-milestone1"
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.vertx:vertx-web"
},
"ranges": [
{
"events": [
{
"introduced": "4.0.0-milestone2"
},
{
"fixed": "4.0.0-milestone5"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.0.0-milestone2"
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.vertx:vertx-web"
},
"ranges": [
{
"events": [
{
"introduced": "4.0.0-milestone3"
},
{
"fixed": "4.0.0-milestone5"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.0.0-milestone3"
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.vertx:vertx-web"
},
"ranges": [
{
"events": [
{
"introduced": "4.0.0-milestone4"
},
{
"fixed": "4.0.0-milestone5"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.0.0-milestone4"
]
}
],
"aliases": [
"CVE-2020-35217"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": true,
"github_reviewed_at": "2021-04-20T17:07:06Z",
"nvd_published_at": "2021-01-20T13:15:00Z",
"severity": "HIGH"
},
"details": "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.",
"id": "GHSA-9q69-g5gc-9fgf",
"modified": "2021-04-20T17:07:06Z",
"published": "2021-04-22T16:16:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-35217"
},
{
"type": "WEB",
"url": "https://github.com/vert-x3/vertx-web/pull/1613"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Cross-Site Request Forgery in Vert.x-Web framework"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…