CVE-2020-3264 json
Cisco SD-WAN Solution Buffer Overflow Vulnerability
published 6y ago modified 4mo ago also EUVD-2020-24535
- cvss
- 7.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
A vulnerability in Cisco SD-WAN Solution software could allow an authenticated, local attacker to cause a buffer overflow on an affected device. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by sending crafted traffic to an affected device. A successful exploit could allow the attacker to gain access to information that they are not authorized to access and make changes to the system that they are not authorized to make.
Patch / fix
- cisco sd-wan_firmware 18.4.5, 19.2.2
Is CVE-2020-3264 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/orangecertcc/security-research/security/advisories/GHSA-wwq2-pxrj-v62r referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.1 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 6.6 | AV:L/AC:L/Au:N/C:C/I:C/A:N |
Affected products
- Cisco Cisco SD-WAN Solution
Classification
References
-
github.com
/orangecertcc/security-research/security/advisories/GHSA-wwq2-pxrj-v62r
exploit, third-party-advisory
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwanbo-QKcABnS2
vendor-advisory
Sources
- CVE List CVE-2020-3264
- NVD CVE-2020-3264
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.