CVE-2020-24703 [High] | Security Vulnerability in Api Manager

An issue was discovered in certain WSO2 products. A valid Carbon Management Console session cookie may be sent to an attacker-controlled server if the victim submits a crafted Try It request, aka Session Hijacking. This affects API Manager 2.2.0, API Manager Analytics 2.2.0, API Microgateway 2.2.0, Data Analytics Server 3.2.0, Enterprise Integrator through 6.6.0, IS as Key Manager 5.5.0, Identity Server 5.5.0 and 5.8.0, Identity Server Analytics 5.5.0, and IoT Server 3.3.0 and 3.3.1.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-03-30	0.77%	0.40%	-0.37%
2	2025-03-29	0.40%	0.77%	+0.37%
3	2025-03-17	—	0.40%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-03-30

0.77%

0.40%

-0.37%

2025-03-29

0.40%

0.77%

+0.37%

2025-03-17

—

0.40%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. 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:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. 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.	2.8	5.9	[email protected]
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. 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:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. 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.	2.8	5.9	[email protected]
6.8	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	8.6	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.

2.8

5.9

[email protected]

8.8

3.1

HIGH

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.

2.8

5.9

[email protected]

6.8

2.0

MEDIUM

AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

8.6

6.4

[email protected]

Affected software / configurations for CVE-2020-24703

Vendor	Product	Version	Raw CPE
wso2	api_manager	2.2.0	cpe:2.3:a:wso2:api_manager:2.2.0:::::::*
wso2	api_manager_analytics	2.2.0	cpe:2.3:a:wso2:api_manager_analytics:2.2.0:::::::*
wso2	api_microgateway	2.2.0	cpe:2.3:a:wso2:api_microgateway:2.2.0:::::::*
wso2	data_analytics_server	3.2.0	cpe:2.3:a:wso2:data_analytics_server:3.2.0:::::::*
wso2	enterprise_integrator	<= 6.6.0	cpe:2.3:a:wso2:enterprise_integrator::::::::
wso2	identity_server	5.5.0	cpe:2.3:a:wso2:identity_server:5.5.0:::::::*
wso2	identity_server	5.8.0	cpe:2.3:a:wso2:identity_server:5.8.0:::::::*
wso2	identity_server_analytics	5.5.0	cpe:2.3:a:wso2:identity_server_analytics:5.5.0:::::::*
wso2	identity_server_as_key_manager	5.5.0	cpe:2.3:a:wso2:identity_server_as_key_manager:5.5.0:::::::*
wso2	iot_server	3.3.0	cpe:2.3:a:wso2:iot_server:3.3.0:::::::*
wso2	iot_server	3.3.1	cpe:2.3:a:wso2:iot_server:3.3.1:::::::*

References for CVE-2020-24703

URL	Tags
https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2020/WSO2-2020-0687/

URL

CVE-2020-24703

Exploit prediction scoring system (EPSS) score for CVE-2020-24703

Common vulnerability scoring system (CVSS) metrics for CVE-2020-24703

Weakness enumeration for CVE-2020-24703

Affected software / configurations for CVE-2020-24703

References for CVE-2020-24703