dbcve.org
GrpcApplication

CVE-2023-4785

HIGH · 7.5 CVSS v3.1 Published 2023-09-13
Fix available
A fix is available. Upgrade to 1.53.2 / 1.54.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrpcApplication
Affected:>= 1.23.0, < 1.53.2>= 1.54.0, < 1.54.3>= 1.55.0, < 1.55.3= 1.56.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.53.2 / 1.54.3 / 1.55.3 or later
Fixed in 1.53.21.54.31.55.3
Vendor patch github.com →
Recommended fix High confidence

Upgrade to gRPC 1.53.2+ (if on 1.53.x), 1.54.3+ (if on 1.54.x), 1.55.3+ (if on 1.55.x), or 1.57.0+ (if on 1.56.0). For older versions, upgrade to 1.53.x or later.

  1. 1. Identify the currently installed gRPC version in your project by checking your dependency configuration files (e.g., requirements.txt for Python, Gemfile for Ruby, or CMake/Conan for C++).
  2. 2. Determine which affected branch your current version falls into based on the version number.
  3. 3. For the 1.53.x branch: upgrade to version 1.53.2 or later (e.g., 1.53.3, 1.53.4, etc.).
  4. 4. For the 1.54.x branch: upgrade to version 1.54.3 or later (e.g., 1.54.4, 1.54.5, etc.).
  5. 5. For the 1.55.x branch: upgrade to version 1.55.3 or later (e.g., 1.55.4, 1.55.5, etc.).
  6. 6. For version 1.56.0: upgrade to version 1.57.0 or later (the next major/minor release).
  7. 7. For versions >=1.23.0 but <1.53.2 on older branches: upgrade to the latest available version in the 1.53.x line (1.53.x) or a newer stable branch.
  8. 8. Update your dependency files with the new version and regenerate lock files.
Caveat Minor: Ensure compatibility with newer gRPC versions in your language-specific binding (C++, Python, or Ruby). Review release notes for any API deprecations between your current and target version.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4785 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4785 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data