Skip to content

SSRF vulnerability in Webhook Dispatcher

High
PhilReinking published GHSA-crgq-9m43-p6qr Nov 7, 2023

Package

composer deck9/input (Composer)

Affected versions

< 1.7.0

Patched versions

1.7.1

Description

The webhooks can use arbitrary URL as input and the request results can be retrieved back through the /api/forms/{form}/submissions endpoint.

This is a full SSRF vulnerability.

As an example, set up a server on localhost and listen on port 8000, then use http://localhost:8000/ as webhook URL, a request would be sent to localhost:8000 and the response is exposed.

This could lead to disclosure of secret information or bypass of firewalls.

You can learn more about SSRF at https://owasp.org/Top10/A10_2021-Server-Side_Request_Forgery_%28SSRF%29/
For fix, you can take a look at https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html, and https://symfony.com/doc/current/http_client.html#ssrf-server-side-request-forgery-handling

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVE ID

No known CVE

Weaknesses

Credits