Metrics
Affected Vendors & Products
Solution
No solution given by the vendor.
Workaround
To avoid the risk associated with this vulnerability, it is recommended to include a secret in all requests that may generate a change in the application's data. A secret is understood, for example, as an extra parameter, generated and sent to the client when accessing the web resource from which the request to be protected is launched. This secret must be generated randomly and be different for each request to be made. On the server side, the application must check that these requests, which cause significant modifications to the data, include the previously generated secrets. If this is not included or is erroneous, the application should not perform the corresponding action. In addition to this secret, it is recommended to set the "SameSite" attribute in the session cookie with the following values: - SameSite=Strict: this value prevents the cookie from being sent in any cross-origin request. - SameSite=Lax: this is the value that is recommended in this case as any action carried out via POST or via a script from a cross-origin will be rejected by the browser.
Wed, 13 Nov 2024 23:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|

Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2025-07-31T12:38:10.983Z
Reserved: 2023-09-14T09:07:57.784Z
Link: CVE-2023-4959

Updated: 2024-08-02T07:44:53.219Z

Status : Modified
Published: 2023-09-15T10:15:07.697
Modified: 2024-11-21T08:36:20.640
Link: CVE-2023-4959


No data.