Cybersecurity Vulnerabilities

Typebot Under Attack: Critical SSRF Vulnerability Exposes AWS Infrastructure (CVE-2025-64709)

Overview

A critical Server-Side Request Forgery (SSRF) vulnerability, identified as CVE-2025-64709, has been discovered in Typebot, an open-source chatbot builder. This flaw, present in versions prior to 3.13.1, allows authenticated users to potentially compromise an entire AWS infrastructure by exploiting the webhook block (HTTP Request component) to access the AWS Instance Metadata Service (IMDS).

Technical Details

The vulnerability resides within the HTTP Request functionality of Typebot’s webhook block. An authenticated user can craft malicious requests that are executed by the Typebot server. Specifically, the vulnerability allows for the injection of custom headers, which can be used to bypass IMDSv2 protections. By injecting headers and crafting requests directed towards the IMDS endpoint (http://169.254.169.254/latest/meta-data/), an attacker can retrieve sensitive information, including temporary AWS IAM credentials associated with the EKS node role.

The process of exploitation typically involves:

  1. Creating a Typebot flow that includes a webhook block.
  2. Configuring the webhook block to make a request.
  3. Crafting the request with a manipulated URL pointing to the IMDS endpoint (http://169.254.169.254/latest/meta-data/iam/security-credentials/<role-name>).
  4. Injecting headers to bypass IMDSv2, such as manipulating the Host header or adding other arbitrary headers to confuse the service.
  5. Retrieving the AWS IAM credentials from the response.

A successful exploit allows an attacker to assume the EKS node role, granting them significant privileges within the Kubernetes cluster and, crucially, access to the wider AWS infrastructure governed by that role’s permissions.

CVSS Analysis

  • CVE ID: CVE-2025-64709
  • Severity: CRITICAL
  • CVSS Score: 9.6

A CVSS score of 9.6 indicates a critical vulnerability due to the ease of exploitation (requiring only authenticated access), the potential for complete system compromise, and the high impact on confidentiality, integrity, and availability.

Possible Impact

The exploitation of CVE-2025-64709 can have severe consequences:

  • Complete Compromise of Kubernetes Cluster: Attackers gain control over the EKS cluster.
  • AWS Infrastructure Takeover: The compromised EKS node role provides access to the broader AWS infrastructure, potentially leading to data breaches, resource hijacking, and denial-of-service attacks.
  • Data Exfiltration: Sensitive data stored within the AWS environment can be exfiltrated.
  • Privilege Escalation: Attackers can use the compromised credentials to further escalate privileges and gain access to other AWS resources.
  • Service Disruption: Attackers can disrupt or completely shut down critical services running on the compromised infrastructure.

Mitigation and Patch Steps

The vulnerability is resolved in Typebot version 3.13.1. Immediate action is required to mitigate the risk:

  1. Upgrade Typebot: Upgrade to version 3.13.1 or later as soon as possible.
  2. Review Webhook Configurations: Inspect all existing webhook configurations for suspicious URLs and headers.
  3. Network Segmentation: Implement network segmentation to limit the impact of a compromised Typebot instance. Consider restricting network access for the Typebot server to only the necessary resources.
  4. Monitor for Suspicious Activity: Monitor network traffic and AWS CloudTrail logs for any suspicious activity related to the Typebot server, such as requests to the IMDS endpoint.
  5. Principle of Least Privilege: Ensure that the EKS node role associated with the Typebot instance follows the principle of least privilege. Grant only the necessary permissions to the role.

References

Cybersecurity specialist and founder of Gowri Shankar Infosec - a professional blog dedicated to sharing actionable insights on cybersecurity, data protection, server administration, and compliance frameworks including SOC 2, PCI DSS, and GDPR.

Leave a Reply

Your email address will not be published. Required fields are marked *