admin/cvelist
1
0
Fork 0
mirror of https://github.com/CVEProject/cvelist.git synced 2025-06-21 05:40:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

"-Synchronized-Data."

Browse Source
This commit is contained in:
CVE Team 2020-12-18 18:01:56 +00:00
parent a5f8075f12
commit a4b9ec6611
No known key found for this signature in database
GPG Key ID: 5708902F06FEF743
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
2020/26xxx/CVE-2020-26251.json
View File

@ -35,7 +35,7 @@
"description_data": [
{
"lang": "eng",
"value": "Open Zaak is a modern, open-source data- and services-layer to enable zaakgericht werken, a Dutch approach to case management.\nIn Open Zaak before version 1.3.3 the Cross-Origin-Resource-Sharing policy in Open Zaak is currently wide open - every client is allowed.\nThis allows evil.com to run scripts that perform AJAX calls to known Open Zaak installations, and the browser will not block these. This was intended to only apply to development machines running on localhost/127.0.0.1.\n\nOpen Zaak 1.3.3 disables CORS by default, while it can be opted-in through environment variables.\n\nThe vulnerability does not actually seem exploitable because:\na) The session cookie has a `Same-Site: Lax` policy which prevents it from being sent along in Cross-Origin requests.\nb) All pages that give access to (production) data are login-protected\nc) `Access-Control-Allow-Credentials` is set to `false`\nd) CSRF checks probably block the remote origin, since they're not explicitly added to the trusted allowlist.\n"
"value": "Open Zaak is a modern, open-source data- and services-layer to enable zaakgericht werken, a Dutch approach to case management. In Open Zaak before version 1.3.3 the Cross-Origin-Resource-Sharing policy in Open Zaak is currently wide open - every client is allowed. This allows evil.com to run scripts that perform AJAX calls to known Open Zaak installations, and the browser will not block these. This was intended to only apply to development machines running on localhost/127.0.0.1. Open Zaak 1.3.3 disables CORS by default, while it can be opted-in through environment variables. The vulnerability does not actually seem exploitable because: a) The session cookie has a `Same-Site: Lax` policy which prevents it from being sent along in Cross-Origin requests. b) All pages that give access to (production) data are login-protected c) `Access-Control-Allow-Credentials` is set to `false` d) CSRF checks probably block the remote origin, since they're not explicitly added to the trusted allowlist."
}
]
},