Skip to main content
← Vulnerabilities

Google::Auth versions from 0.11 through 0.12 for Perl accept an authorization code from any local process because the gcloud-auth login…

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Published
Last modified
Published
Not listed in CISA KEV
5/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The Google::Auth Perl library (versions 0.11 through 0.12) and the gcloud CLI's login flow are affected. A local attacker on the same machine can slip their own Google account's authorization code into the login callback, so the user's tools end up running under the attacker's account instead of the user's.

Read the original description

Google::Auth versions from 0.11 through 0.12 for Perl accept an authorization code from any local process because the gcloud-auth login callback does not check the OAuth state. The gcloud-auth login and application-default login commands send a state parameter with the authorization request, then take the code from the first request to reach their loopback listener without comparing the returned state. A local attacker can submit an authorization code for their own Google account. The CLI exchanges it and stores the refresh token as the user's credentials, so the user's tools then act as the attacker's account.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Google-Auth

    From 0.11 · through 0.12

Evidence 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.