What is GHSA-3GJW-F78C-VVPW?

GHSA-3GJW-F78C-VVPW is a medium-severity out-of-bounds read vulnerability in tokio-postgres (rust), affecting versions >= 0.4.0, < 0.7.18. It is fixed in 0.7.18. A read operation accesses a memory location beyond the intended buffer boundary.

Which versions of tokio-postgres are affected by GHSA-3GJW-F78C-VVPW?

tokio-postgres (rust) versions >= 0.4.0, < 0.7.18 is affected.

Is there a fix for GHSA-3GJW-F78C-VVPW?

Yes. GHSA-3GJW-F78C-VVPW is fixed in 0.7.18. Upgrade to this version or later.

Is GHSA-3GJW-F78C-VVPW exploitable, and should I be worried?

Whether GHSA-3GJW-F78C-VVPW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-3GJW-F78C-VVPW is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-3GJW-F78C-VVPW in tokio-postgres

Q: Which versions of tokio-postgres are affected by GHSA-3GJW-F78C-VVPW?

tokio-postgres (rust) versions >= 0.4.0, < 0.7.18 is affected.

Q: Is there a fix for GHSA-3GJW-F78C-VVPW?

Yes. GHSA-3GJW-F78C-VVPW is fixed in 0.7.18. Upgrade to this version or later.

Q: Is GHSA-3GJW-F78C-VVPW exploitable, and should I be worried?

Whether GHSA-3GJW-F78C-VVPW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-3GJW-F78C-VVPW is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-3GJW-F78C-VVPW?

Upgrade tokio-postgres to 0.7.18 or later.

Summary

tokio-postgres: Panic on a DataRow with fewer fields than columns allows denial of service

A malicious or compromised server can send a row containing fewer fields than
its row description declares columns. Reading one of the missing columns then
panics with an out-of-bounds index, aborting the calling task. This affects even
the otherwise non-panicking try_get, and both Row and SimpleQueryRow.

Applications that connect only to a trusted database are not exposed; the risk
applies to clients that may connect to untrusted or user-supplied servers, or
whose connection can be intercepted by a man-in-the-middle.

Impact

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

Affected versions

tokio-postgres (>= 0.4.0, < 0.7.18)

Security releases

tokio-postgres → 0.7.18 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade tokio-postgres to 0.7.18 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-3GJW-F78C-VVPW? GHSA-3GJW-F78C-VVPW is a medium-severity out-of-bounds read vulnerability in tokio-postgres (rust), affecting versions >= 0.4.0, < 0.7.18. It is fixed in 0.7.18. A read operation accesses a memory location beyond the intended buffer boundary.
Which versions of tokio-postgres are affected by GHSA-3GJW-F78C-VVPW? tokio-postgres (rust) versions >= 0.4.0, < 0.7.18 is affected.
Is there a fix for GHSA-3GJW-F78C-VVPW? Yes. GHSA-3GJW-F78C-VVPW is fixed in 0.7.18. Upgrade to this version or later.
Is GHSA-3GJW-F78C-VVPW exploitable, and should I be worried? Whether GHSA-3GJW-F78C-VVPW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-3GJW-F78C-VVPW is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-3GJW-F78C-VVPW? Upgrade tokio-postgres to 0.7.18 or later.