CVE-2024-32973

Traffic tampering via non-CA certificate trust

Published May 1, 2024 · Updated Aug 2, 2024

Improper TLS peer verification in Pluto 0.9.0 through 0.9.2 allows man-in-the-middle attackers to tamper with protected traffic. The HTTP library and socket.starttls TLS verification path accepts a non-CA certificate as a CA trust anchor instead of rejecting it. Exploitation requires active traffic interception and a crafted certificate, affects non-WASM builds, and compromises transport integrity without reported disclosure or service interruption.

CVSS severity4.8
Medium
EPSS probability0.13%
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

Improper TLS peer verification in Pluto 0.9.0 through 0.9.2 allows man-in-the-middle attackers to tamper with protected traffic. The HTTP library and socket.starttls TLS verification path accepts a non-CA certificate as a CA trust anchor instead of rejecting it. Exploitation requires active traffic interception and a crafted certificate, affects non-WASM builds, and compromises transport integrity without reported disclosure or service interruption.

The record

CVE
CVE-2024-32973
Published
May 1, 2024
Updated
Aug 2, 2024
Vendor
PlutoLang
Product
Pluto
Classifications
CWE-284, T1557
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 1, 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=>= 0.9.0, < 0.9.3
  2. Affected versionversion=0.9.0 <0.9.3

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

PlutoLang · Plutoversion=>= 0.9.0, < 0.9.3; version=0.9.0 <0.9.3

Published CVSS scores

4.8GitHub, Inc.CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:N/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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-284Improper Access Control
T1557Adversary-in-the-Middle

Public exploit references

No public exploit references are available in this record.

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