CyberSecBulletin
CVE-2024-21527NVD status: Deferred

github.com/gotenberg/gotenberg/v8/pkg/gotenberg: Server-Side Request Forgery

Published Updated By the CyberSecBulletin desk

CVE-2024-21527 is a high-severity server-side request forgery vulnerability in github.com/gotenberg/gotenberg/v8/pkg/gotenberg, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 8.1.0 as the first without the flaw, so updating github.com/gotenberg/gotenberg/v8/pkg/gotenberg to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.57% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update github.com/gotenberg/gotenberg/v8/pkg/gotenberg to 8.1.0 or a later version.
  2. Update github.com/gotenberg/gotenberg/v8/pkg/modules/chromium to 8.1.0 or a later version.
  3. Update github.com/gotenberg/gotenberg/v8/pkg/modules/webhook to 8.1.0 or a later version.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Github.com/gotenberg/gotenberg/v8/pkg/gotenberggithub.com/gotenberg/gotenberg/v8/pkg/gotenbergbefore 8.1.08.1.0
Github.com/gotenberg/gotenberg/v8/pkg/modules/chromiumgithub.com/gotenberg/gotenberg/v8/pkg/modules/chromiumbefore 8.1.08.1.0
Github.com/gotenberg/gotenberg/v8/pkg/modules/webhookgithub.com/gotenberg/gotenberg/v8/pkg/modules/webhookbefore 8.1.08.1.0
Gotenberggotenbergbefore 8.1.08.1.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
LowLimited modification of data is possible.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N. Scored by CNA (snyk.io).

Scoring systemScoreSeverityScored by
CVSS 4.07.8HighCNA (snyk.io)
CVSS 3.18.2HighCNA (snyk.io)

Official description

Versions of the package github.com/gotenberg/gotenberg/v8/pkg/gotenberg before 8.1.0; versions of the package github.com/gotenberg/gotenberg/v8/pkg/modules/chromium before 8.1.0; versions of the package github.com/gotenberg/gotenberg/v8/pkg/modules/webhook before 8.1.0 are vulnerable to Server-side Request Forgery (SSRF) via the /convert/html endpoint when a request is made to a file via localhost, such as <iframe src="\\localhost/etc/passwd">. By exploiting this vulnerability, an attacker can achieve local file inclusion, allowing of sensitive files read on the host system. Workaround An alternative is using either or both --chromium-deny-list and --chromium-allow-list flags.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Server-Side Request Forgery

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

How developers prevent this class of flaw

  • If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
  • If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.

More Server-Side Request Forgery vulnerabilities (CWE-918)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Server-Side Request Forgery vulnerabilities

Spotted an error? Tell us.