Java Facebook Thrift servers would not error upon receiving messages with containers of fields of unknown type.

published 2019-05-06 7y ago modified 2026-06-17 4mo ago also EUVD-2019-13196

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.0%; EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits: 0; none known

Java 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.02.18.00.

Patch / fix

fixed in 1 links 1

Facebook Facebook Thrift v2019.02.18.00

github.com/facebook/fbthrift@a56346c commit

Is CVE-2019-3559 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.99% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

Facebook Facebook Thrift

Classification

Weakness

CWE-834 Excessive Iteration
CWE-755 Improper Handling of Exceptional Conditions

References

github.com /facebook/fbthrift/commit/a56346ceacad28bf470017a6bda1d5518d0bd943
patch, third-party-advisory
facebook.com /security/advisories/cve-2019-3559
vendor-advisory
lists.apache.org /thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E
mailing-list

Sources

CVE List CVE-2019-3559
NVD CVE-2019-3559

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.