CVE-2018-20840
An unhandled exception vulnerability exists during Google Sign-In with Google API C++ Client before 2019-04-10.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.65%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
An unhandled exception vulnerability exists during Google Sign-In with Google API C++ Client before 2019-04-10. It potentially causes an outage of third-party services that were not designed to recover from exceptions. On the client, ID token handling can cause an unhandled exception because of misinterpretation of an integer as a string, resulting in denial-of-service and then other users can no longer login/sign-in to the affected third-party service. Once this third-party service uses Google Sign-In with google-api-cpp-client, a malicious user can trigger this client/auth/oauth2_authorization.cc vulnerability by requesting the client to receive the ID token from a Google authentication server.
- CVSS 3.0
- 8.6 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
- EPSS
- 0.65% probability · 49th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-754
- Affected
- google/api c\+\+ client
- Source
- cve@mitre.org
References
- https://github.com/google/google-api-cpp-client/issues/57Exploit, Issue Tracking, Third Party Advisory
- https://github.com/google/google-api-cpp-client/pull/58Issue Tracking, Patch, Third Party Advisory
- https://github.com/google/google-api-cpp-client/issues/57Exploit, Issue Tracking, Third Party Advisory
- https://github.com/google/google-api-cpp-client/pull/58Issue Tracking, Patch, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.