FKIE_CVE-2022-20717
Vulnerability from fkie_nvd - Published: 2022-04-15 15:15 - Updated: 2026-06-17 04:24| Vendor | Product | Version | |
|---|---|---|---|
| cisco | sd-wan_vedge_router | * | |
| cisco | sd-wan_vedge_router | 20.7 | |
| cisco | 1100_integrated_services_router | - | |
| citrix | sd-wan_1000 | - | |
| citrix | sd-wan_110 | - | |
| citrix | sd-wan_1100 | - | |
| citrix | sd-wan_2000 | - | |
| citrix | sd-wan_210 | - | |
| citrix | sd-wan_2100 | - | |
| citrix | sd-wan_5100 | - |
{
"affected": [
{
"affectedData": [
{
"product": "Cisco SD-WAN vEdge router",
"vendor": "Cisco",
"versions": [
{
"status": "affected",
"version": "n/a"
}
]
}
],
"source": "psirt@cisco.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:cisco:sd-wan_vedge_router:*:*:*:*:*:*:*:*",
"matchCriteriaId": "8B7EA8D9-812D-4D62-A5A7-8994BDB0C8E5",
"versionEndIncluding": "20.6",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:cisco:sd-wan_vedge_router:20.7:*:*:*:*:*:*:*",
"matchCriteriaId": "26FADAB8-5A72-4B9D-9E9C-91A69F53B441",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
},
{
"cpeMatch": [
{
"criteria": "cpe:2.3:h:cisco:1100_integrated_services_router:-:*:*:*:*:*:*:*",
"matchCriteriaId": "1952B64C-4AE0-4CCB-86C5-8D1FF6A12822",
"vulnerable": false
},
{
"criteria": "cpe:2.3:h:citrix:sd-wan_1000:-:*:*:*:*:*:*:*",
"matchCriteriaId": "99FC163D-E468-4D98-AE56-D4D29F5C05D7",
"vulnerable": false
},
{
"criteria": "cpe:2.3:h:citrix:sd-wan_110:-:*:*:*:*:*:*:*",
"matchCriteriaId": "6062DBFF-04E4-48D9-A2A0-42BECE9E0EA2",
"vulnerable": false
},
{
"criteria": "cpe:2.3:h:citrix:sd-wan_1100:-:*:*:*:*:*:*:*",
"matchCriteriaId": "3426DD26-48A7-408A-82B4-99CAA82804AF",
"vulnerable": false
},
{
"criteria": "cpe:2.3:h:citrix:sd-wan_2000:-:*:*:*:*:*:*:*",
"matchCriteriaId": "E387174A-1A9C-4A16-9F66-8158F06C89C5",
"vulnerable": false
},
{
"criteria": "cpe:2.3:h:citrix:sd-wan_210:-:*:*:*:*:*:*:*",
"matchCriteriaId": "42DBB6B2-E526-4C12-AED8-245D4E21A011",
"vulnerable": false
},
{
"criteria": "cpe:2.3:h:citrix:sd-wan_2100:-:*:*:*:*:*:*:*",
"matchCriteriaId": "2524E92A-D661-4F31-9026-2F182B68CDC0",
"vulnerable": false
},
{
"criteria": "cpe:2.3:h:citrix:sd-wan_5100:-:*:*:*:*:*:*:*",
"matchCriteriaId": "C022A51A-6D37-4AA9-82B5-19F17EA581CC",
"vulnerable": false
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "A vulnerability in the NETCONF process of Cisco SD-WAN vEdge Routers could allow an authenticated, local attacker to cause an affected device to run out of memory, resulting in a denial of service (DoS) condition. This vulnerability is due to insufficient memory management when an affected device receives large amounts of traffic. An attacker could exploit this vulnerability by sending malicious traffic to an affected device. A successful exploit could allow the attacker to cause the device to crash, resulting in a DoS condition."
},
{
"lang": "es",
"value": "Una vulnerabilidad en el proceso NETCONF de los routers Cisco SD-WAN vEdge podr\u00eda permitir a un atacante local autenticado causar a un dispositivo afectado quedarse sin memoria, resultando en una condici\u00f3n de denegaci\u00f3n de servicio (DoS). Esta vulnerabilidad es debido a una administraci\u00f3n insuficiente de la memoria cuando un dispositivo afectado recibe grandes cantidades de tr\u00e1fico. Un atacante podr\u00eda explotar esta vulnerabilidad mediante el env\u00edo de tr\u00e1fico malicioso a un dispositivo afectado. Una explotaci\u00f3n con \u00e9xito podr\u00eda permitir al atacante causar un bloqueo del dispositivo, resultando en una condici\u00f3n de DoS"
}
],
"id": "CVE-2022-20717",
"lastModified": "2026-06-17T04:24:56.190",
"metrics": {
"cvssMetricV2": [
{
"acInsufInfo": false,
"baseSeverity": "MEDIUM",
"cvssData": {
"accessComplexity": "LOW",
"accessVector": "LOCAL",
"authentication": "NONE",
"availabilityImpact": "COMPLETE",
"baseScore": 4.9,
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"vectorString": "AV:L/AC:L/Au:N/C:N/I:N/A:C",
"version": "2.0"
},
"exploitabilityScore": 3.9,
"impactScore": 6.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"source": "nvd@nist.gov",
"type": "Primary",
"userInteractionRequired": false
}
],
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.0"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "psirt@cisco.com",
"type": "Secondary"
}
],
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2022-20717",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-11-06T15:59:05.080616Z",
"version": "2.0.3"
}
}
]
},
"published": "2022-04-15T15:15:13.113",
"references": [
{
"source": "psirt@cisco.com",
"tags": [
"Vendor Advisory"
],
"url": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-vedge-dos-jerVm4bB"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Vendor Advisory"
],
"url": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-vedge-dos-jerVm4bB"
}
],
"sourceIdentifier": "psirt@cisco.com",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-789"
}
],
"source": "psirt@cisco.com",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-770"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.