CVE-2024-32980Public exploitNetwork attack vector

Arbitrary outbound requests via untrusted Host header

Published May 8, 2024 · Updated Aug 2, 2024

SSRF in Spin before 2.4.3 allows remote attackers to make configured applications send requests to arbitrary hosts via a Host header. The HTTP trigger's set_req_uri function copies the untrusted inbound Host header into the request URI authority, so a relative self request is authorized against an attacker-chosen host. Exploitation requires URL-based upstream routing that preserves Host, a self outbound-host permission, and a component that issues an authority-less request; the response is then treated as internal.

CVSS severity9.1
Critical
EPSS probability0.49%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SSRF in Spin before 2.4.3 allows remote attackers to make configured applications send requests to arbitrary hosts via a Host header. The HTTP trigger's set_req_uri function copies the untrusted inbound Host header into the request URI authority, so a relative self request is authorized against an attacker-chosen host. Exploitation requires URL-based upstream routing that preserves Host, a self outbound-host permission, and a component that issues an authority-less request; the response is then treated as internal.

The record

CVE
CVE-2024-32980
Published
May 8, 2024
Updated
Aug 2, 2024
Vendor
spinframework
Product
Spin
Classifications
CWE-610, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 8, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.4.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

spinframework · Spinversion=< 2.4.3

Published CVSS scores

9.1GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-610Externally Controlled Reference to a Resource in Another Sphere
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo