Skip to content
Fencer Intel
high 7.5

CVE-2020-1469 json

Infinite loop in .Net Bond

published 6y ago modified 4mo ago also GHSA-rqrc-8q8f-cp9c , EUVD-2022-1826

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

Summary

A denial of service vulnerability exists when the .NET implementation of Bond improperly parses input, aka 'Bond Denial of Service Vulnerability'.

Patch / fix

  • nuget Bond.Core.CSharp 9.0.1

Is CVE-2020-1469 in your dependencies? 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

4.84% chance of exploitation in the next 30 days, higher than 92% 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
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
nuget Bond.Core.CSharp
>=3.0.0, <9.0.1
9.0.1

Affected products

  • Microsoft Bond 9.0.1

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type
  • CWE-835 Loop with Unreachable Exit Condition

References

Sources

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.