FKIE_CVE-2021-1593
Vulnerability from fkie_nvd - Published: 2021-08-04 18:15 - Updated: 2026-06-17 03:327.3 (High) - CVSS:3.1/
| Vendor | Product | Version | |
|---|---|---|---|
| cisco | packet_tracer | 7.2.0 | |
| cisco | packet_tracer | 7.2.1 | |
| cisco | packet_tracer | 7.2.2 | |
| cisco | packet_tracer | 7.3.0 | |
| cisco | packet_tracer | 7.3.1 | |
| cisco | packet_tracer | 8.0 |
{
"affected": [
{
"affectedData": [
{
"product": "Cisco Packet Tracer",
"vendor": "Cisco",
"versions": [
{
"status": "affected",
"version": "n/a"
}
]
}
],
"source": "psirt@cisco.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:cisco:packet_tracer:7.2.0:*:*:*:*:*:*:*",
"matchCriteriaId": "4C0B5794-4105-4803-A2CF-E56AAD49F194",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:cisco:packet_tracer:7.2.1:*:*:*:*:*:*:*",
"matchCriteriaId": "D1C996C9-E9E0-4C11-8469-BB35F7851218",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:cisco:packet_tracer:7.2.2:*:*:*:*:*:*:*",
"matchCriteriaId": "431D10F3-9327-4A56-8A34-2C18AFF94B96",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:cisco:packet_tracer:7.3.0:*:*:*:*:*:*:*",
"matchCriteriaId": "582FDF29-ECB1-41B5-97F3-2FE06972A8B1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:cisco:packet_tracer:7.3.1:*:*:*:*:*:*:*",
"matchCriteriaId": "79BE4C76-E984-4654-8B40-D228039C8AFD",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:cisco:packet_tracer:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "8AED375D-9B82-450E-AC3D-E7FEA285E08B",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "A vulnerability in Cisco Packet Tracer for Windows could allow an authenticated, local attacker to perform a DLL injection attack on an affected device. To exploit this vulnerability, the attacker must have valid credentials on the Windows system. This vulnerability is due to incorrect handling of directory paths at run time. An attacker could exploit this vulnerability by inserting a configuration file in a specific path on the system, which can cause a malicious DLL file to be loaded when the application starts. A successful exploit could allow an attacker with normal user privileges to execute arbitrary code on the affected system with the privileges of another user\u0026rsquo;s account."
},
{
"lang": "es",
"value": "Una vulnerabilidad en Cisco Packet Tracer para Windows, podr\u00eda permitir a un atacante local autenticado llevar a cabo un ataque de inyecci\u00f3n DLL en un dispositivo afectado. Para explotar esta vulnerabilidad, el atacante debe tener credenciales v\u00e1lidas en el sistema Windows. Esta vulnerabilidad es debido al manejo incorrecto de las rutas de directorio en tiempo de ejecuci\u00f3n. Un atacante podr\u00eda explotar esta vulnerabilidad al insertar un archivo de configuraci\u00f3n en una ruta espec\u00edfica del sistema, lo que puede causar que se cargue un archivo DLL malicioso cuando se inicie la aplicaci\u00f3n. Una explotaci\u00f3n con \u00e9xito podr\u00eda permitir a un atacante con privilegios de usuario normales ejecutar c\u00f3digo arbitrario en el sistema afectado con los privilegios de la cuenta de otro usuario"
}
],
"id": "CVE-2021-1593",
"lastModified": "2026-06-17T03:32:07.710",
"metrics": {
"cvssMetricV2": [
{
"acInsufInfo": false,
"baseSeverity": "MEDIUM",
"cvssData": {
"accessComplexity": "MEDIUM",
"accessVector": "LOCAL",
"authentication": "NONE",
"availabilityImpact": "COMPLETE",
"baseScore": 6.9,
"confidentialityImpact": "COMPLETE",
"integrityImpact": "COMPLETE",
"vectorString": "AV:L/AC:M/Au:N/C:C/I:C/A:C",
"version": "2.0"
},
"exploitabilityScore": 3.4,
"impactScore": 10.0,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"source": "nvd@nist.gov",
"type": "Primary",
"userInteractionRequired": true
}
],
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.3,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.3,
"impactScore": 5.9,
"source": "psirt@cisco.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.3,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.3,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2021-1593",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-11-07T21:43:29.206748Z",
"version": "2.0.3"
}
}
]
},
"published": "2021-08-04T18:15:08.633",
"references": [
{
"source": "psirt@cisco.com",
"tags": [
"Vendor Advisory"
],
"url": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-packettracer-dll-inj-Qv8Mk5Jx"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Vendor Advisory"
],
"url": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-packettracer-dll-inj-Qv8Mk5Jx"
}
],
"sourceIdentifier": "psirt@cisco.com",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-427"
}
],
"source": "psirt@cisco.com",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-427"
}
],
"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.