Cpe:2.3:a:utcp:utcp-Http:*:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3autcputcp-http/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSun, 27 Sep 2026 19:09:13 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgCredential Exfiltration via Unvalidated OAuth2 TokenUrl in utcp-httphttps://feed.craftedsignal.io/briefs/2026-09-utcp-http-auth-bypass/Sun, 27 Sep 2026 19:09:13 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-utcp-http-auth-bypass/The utcp-http library before version 1.1.4 fails to validate the OAuth2 tokenUrl field in remote OpenAPI specifications, allowing attackers to redirect and capture client credentials.The utcp-http library, version 1.1.4 and prior, contains a critical vulnerability related to the improper validation of the OAuth2 tokenUrl field retrieved from remote OpenAPI specifications. When a developer or user registers a malicious or compromised OpenAPI specification, the library blindly processes the provided tokenUrl value. Upon invoking a tool generated from this specification, the library performs an automated HTTP POST request to the attacker-defined endpoint. This request includes the victim's client_id and client_secret credentials, effectively exfiltrating them to an arbitrary destination under the attacker's control. This vulnerability poses a significant risk to applications relying on utcp-http for OAuth2-protected tool integration, as it facilitates credential theft through the manipulation of remote schema definitions.

Impact

Successful exploitation allows for the theft of OAuth2 client_id and client_secret credentials, potentially leading to unauthorized access to downstream services or APIs protected by these credentials. If the stolen credentials provide broad permissions, the impact could extend to significant data exposure or unauthorized actions within the victim's integrated services.

Recommendation

  • Upgrade the utcp-http library to version 1.1.4 or later immediately to incorporate necessary URL validation logic.
  • Audit all currently registered or dynamically loaded OpenAPI specifications to ensure that the tokenUrl fields point to trusted and expected domains.
  • Implement strict allowlisting for domains allowed in the OAuth2 configuration if dynamic remote specification loading is required.
]]>highadvisory