gRPC: Uncaught Exception
CVE-2023-4785 is a high-severity uncaught exception vulnerability in gRPC from Google, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected gRPC versions: 1.56.0 through 1.56.1; 1.55.0 through 1.55.2; 1.54.0 through 1.54.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.77% chance of exploitation within 30 days, higher than 56% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update grpc to 1.23 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| gRPC | 1.56.0 through 1.56.1; 1.55.0 through 1.55.2; 1.54.0 through 1.54.2; 1.53.0 through 1.53.1 | Not stated | |
| Grpc | grpc | before 1.23; 1.57; 1.56.0 through 1.56.1; 1.55.0 through 155.2; 1.54.0 through 1.54.2; 1.53.0 through 1.53.1 | 1.23 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (google.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
Lack of error handling in the TCP server in Google's gRPC starting version 1.23 on posix-compatible platforms (ex. Linux) allows an attacker to cause a denial of service by initiating a significant number of connections with the server. Note that gRPC C++ Python, and Ruby are affected, but gRPC Java, and Go are NOT affected.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Uncaught Exception
An exception is thrown from a function, but it is not caught.
How developers prevent this class of flaw
- The choice between a language which has named or unnamed exceptions needs to be done. While unnamed exceptions exacerbate the chance of not properly dealing with an exception, named exceptions suffer from the up call version of the weak base class problem.
- A language can be used which requires, at compile time, to catch all serious exceptions. However, one must make sure to use the most current version of the API as new exceptions could be added.
- Catch all relevant exceptions. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/grpc/grpc/pull/33656Issue Tracking
- github.com/grpc/grpc/pull/33667Issue Tracking
- github.com/grpc/grpc/pull/33669Issue Tracking
- github.com/grpc/grpc/pull/33670Issue Tracking
- github.com/grpc/grpc/pull/33672Issue Tracking
Other vulnerabilities in gRPC
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Uncaught Exception vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.