CVE-2019-3564

Improper Input Validation and Excessive Iteration in Go Facebook Thrift

Go Facebook Thrift servers would not error upon receiving messages with containers of fields of unknown type. As a result, malicious clients could send short messages which would take a long time for the server to parse, potentially leading to denial of service. This issue affects Facebook Thrift prior to v2019.03.04.00.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2019-3564 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.31.1-0.20190225164308-c461c1bd1a3e); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2019-3564? CVE-2019-3564 is a high-severity improper input validation vulnerability in github.com/facebook/fbthrift (go), affecting versions < 0.31.1-0.20190225164308-c461c1bd1a3e. It is fixed in 0.31.1-0.20190225164308-c461c1bd1a3e. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2019-3564? CVE-2019-3564 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/facebook/fbthrift are affected by CVE-2019-3564? github.com/facebook/fbthrift (go) versions < 0.31.1-0.20190225164308-c461c1bd1a3e is affected.
4. Is there a fix for CVE-2019-3564? Yes. CVE-2019-3564 is fixed in 0.31.1-0.20190225164308-c461c1bd1a3e. Upgrade to this version or later.
5. Is CVE-2019-3564 exploitable, and should I be worried? Whether CVE-2019-3564 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
6. What actually determines whether CVE-2019-3564 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.
7. How do I fix CVE-2019-3564? Upgrade github.com/facebook/fbthrift to 0.31.1-0.20190225164308-c461c1bd1a3e or later.

Other vulnerabilities in github.com/facebook/fbthrift