CVE-2024-20435 [High] | Security Vulnerability in Asyncos

A vulnerability in the CLI of Cisco AsyncOS for Secure Web Appliance could allow an authenticated, local attacker to execute arbitrary commands and elevate privileges to root. This vulnerability is due to insufficient validation of user-supplied input for the CLI. An attacker could exploit this vulnerability by authenticating to the system and executing a crafted command on the affected device. A successful exploit could allow the attacker to execute arbitrary commands on the underlying operating system and elevate privileges to root. To successfully exploit this vulnerability, an attacker would need at least guest credentials.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.14%	0.16%	+0.02%
2	2025-08-29	0.16%	0.14%	-0.02%
3	2025-08-25	—	0.16%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.14%

0.16%

+0.02%

2025-08-29

0.16%

0.14%

-0.02%

2025-08-25

—

0.16%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.0	6.0	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.0

6.0

[email protected]

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

Affected software / configurations for CVE-2024-20435

Vendor	Product	Version	Raw CPE
cisco	asyncos	11.7.0-406	cpe:2.3:o:cisco:asyncos:11.7.0-406:::::::*
cisco	asyncos	11.7.0-418	cpe:2.3:o:cisco:asyncos:11.7.0-418:::::::*
cisco	asyncos	11.7.1-006	cpe:2.3:o:cisco:asyncos:11.7.1-006:::::::*
cisco	asyncos	11.7.1-020	cpe:2.3:o:cisco:asyncos:11.7.1-020:::::::*
cisco	asyncos	11.7.1-049	cpe:2.3:o:cisco:asyncos:11.7.1-049:::::::*
cisco	asyncos	11.7.2-011	cpe:2.3:o:cisco:asyncos:11.7.2-011:::::::*
cisco	asyncos	11.8.0-414	cpe:2.3:o:cisco:asyncos:11.8.0-414:::::::*
cisco	asyncos	11.8.1-023	cpe:2.3:o:cisco:asyncos:11.8.1-023:::::::*
cisco	asyncos	11.8.3-018	cpe:2.3:o:cisco:asyncos:11.8.3-018:::::::*
cisco	asyncos	11.8.3-021	cpe:2.3:o:cisco:asyncos:11.8.3-021:::::::*
cisco	asyncos	12.0.1-268	cpe:2.3:o:cisco:asyncos:12.0.1-268:::::::*
cisco	asyncos	12.0.3-007	cpe:2.3:o:cisco:asyncos:12.0.3-007:::::::*
cisco	asyncos	12.5.1-011	cpe:2.3:o:cisco:asyncos:12.5.1-011:::::::*
cisco	asyncos	12.5.2-007	cpe:2.3:o:cisco:asyncos:12.5.2-007:::::::*
cisco	asyncos	12.5.4-005	cpe:2.3:o:cisco:asyncos:12.5.4-005:::::::*
cisco	asyncos	12.5.5-004	cpe:2.3:o:cisco:asyncos:12.5.5-004:::::::*
cisco	asyncos	12.5.6-008	cpe:2.3:o:cisco:asyncos:12.5.6-008:::::::*
cisco	asyncos	14.0.2-012	cpe:2.3:o:cisco:asyncos:14.0.2-012:::::::*
cisco	asyncos	14.0.3-014	cpe:2.3:o:cisco:asyncos:14.0.3-014:::::::*
cisco	asyncos	14.0.4-005	cpe:2.3:o:cisco:asyncos:14.0.4-005:::::::*
cisco	asyncos	14.0.5-007	cpe:2.3:o:cisco:asyncos:14.0.5-007:::::::*
cisco	asyncos	14.5.0-498	cpe:2.3:o:cisco:asyncos:14.5.0-498:::::::*
cisco	asyncos	14.5.1-016	cpe:2.3:o:cisco:asyncos:14.5.1-016:::::::*
cisco	asyncos	14.5.2-011	cpe:2.3:o:cisco:asyncos:14.5.2-011:::::::*
cisco	asyncos	15.0.0-322	cpe:2.3:o:cisco:asyncos:15.0.0-322:::::::*
cisco	asyncos	15.0.0-355	cpe:2.3:o:cisco:asyncos:15.0.0-355:::::::*
cisco	asyncos	15.1.0-287	cpe:2.3:o:cisco:asyncos:15.1.0-287:::::::*

References for CVE-2024-20435

URL	Tags
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-swa-priv-esc-7uHpZsCC	Vendor Advisory

URL

CVE-2024-20435

Exploit prediction scoring system (EPSS) score for CVE-2024-20435

Common vulnerability scoring system (CVSS) metrics for CVE-2024-20435

Weakness enumeration for CVE-2024-20435

Affected software / configurations for CVE-2024-20435

References for CVE-2024-20435