CVE-2022-33232 [Critical] | Security Vulnerability in Aqt1000 Firmware

CVE-2022-33232 is rated Moderate Risk (44.5/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.07%). Review affected assets and schedule remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.05%	0.07%	+0.02%
2	2025-11-18	0.06%	0.05%	-0.01%
3	2025-03-17	—	0.06%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.05%

0.07%

+0.02%

2025-11-18

0.06%

0.05%

-0.01%

2025-03-17

—

0.06%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.3	3.1	CRITICAL	`CVSS:3.1/AV:L/AC:L/PR:N/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:N) No account or special rights needed—anonymous or random user is enough. 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.5	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

9.3

3.1

CRITICAL

CVSS:3.1/AV:L/AC:L/PR:N/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:N): No account or special rights needed—anonymous or random user is enough.
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.5

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-2022-33232

Vendor	Product	Version	Raw CPE
qualcomm	aqt1000_firmware	—	cpe:2.3:o:qualcomm:aqt1000_firmware:-:::::::*
qualcomm	ar8035_firmware	—	cpe:2.3:o:qualcomm:ar8035_firmware:-:::::::*
qualcomm	qam8295p_firmware	—	cpe:2.3:o:qualcomm:qam8295p_firmware:-:::::::*
qualcomm	qca6174a_firmware	—	cpe:2.3:o:qualcomm:qca6174a_firmware:-:::::::*
qualcomm	qca6310_firmware	—	cpe:2.3:o:qualcomm:qca6310_firmware:-:::::::*
qualcomm	qca6335_firmware	—	cpe:2.3:o:qualcomm:qca6335_firmware:-:::::::*
qualcomm	qca6390_firmware	—	cpe:2.3:o:qualcomm:qca6390_firmware:-:::::::*
qualcomm	qca6391_firmware	—	cpe:2.3:o:qualcomm:qca6391_firmware:-:::::::*
qualcomm	qca6420_firmware	—	cpe:2.3:o:qualcomm:qca6420_firmware:-:::::::*
qualcomm	qca6421_firmware	—	cpe:2.3:o:qualcomm:qca6421_firmware:-:::::::*
qualcomm	qca6426_firmware	—	cpe:2.3:o:qualcomm:qca6426_firmware:-:::::::*
qualcomm	qca6430_firmware	—	cpe:2.3:o:qualcomm:qca6430_firmware:-:::::::*
qualcomm	qca6431_firmware	—	cpe:2.3:o:qualcomm:qca6431_firmware:-:::::::*
qualcomm	qca6436_firmware	—	cpe:2.3:o:qualcomm:qca6436_firmware:-:::::::*
qualcomm	qca6564a_firmware	—	cpe:2.3:o:qualcomm:qca6564a_firmware:-:::::::*
qualcomm	qca6564au_firmware	—	cpe:2.3:o:qualcomm:qca6564au_firmware:-:::::::*
qualcomm	qca6574_firmware	—	cpe:2.3:o:qualcomm:qca6574_firmware:-:::::::*
qualcomm	qca6574a_firmware	—	cpe:2.3:o:qualcomm:qca6574a_firmware:-:::::::*
qualcomm	qca6574au_firmware	—	cpe:2.3:o:qualcomm:qca6574au_firmware:-:::::::*
qualcomm	qca6595_firmware	—	cpe:2.3:o:qualcomm:qca6595_firmware:-:::::::*
qualcomm	qca6595au_firmware	—	cpe:2.3:o:qualcomm:qca6595au_firmware:-:::::::*
qualcomm	qca6696_firmware	—	cpe:2.3:o:qualcomm:qca6696_firmware:-:::::::*
qualcomm	qca6698aq_firmware	—	cpe:2.3:o:qualcomm:qca6698aq_firmware:-:::::::*
qualcomm	qca8081_firmware	—	cpe:2.3:o:qualcomm:qca8081_firmware:-:::::::*
qualcomm	qca8337_firmware	—	cpe:2.3:o:qualcomm:qca8337_firmware:-:::::::*
qualcomm	qca9377_firmware	—	cpe:2.3:o:qualcomm:qca9377_firmware:-:::::::*
qualcomm	qcm6490_firmware	—	cpe:2.3:o:qualcomm:qcm6490_firmware:-:::::::*
qualcomm	qcn6024_firmware	—	cpe:2.3:o:qualcomm:qcn6024_firmware:-:::::::*
qualcomm	qcn9011_firmware	—	cpe:2.3:o:qualcomm:qcn9011_firmware:-:::::::*
qualcomm	qcn9012_firmware	—	cpe:2.3:o:qualcomm:qcn9012_firmware:-:::::::*
qualcomm	qcn9024_firmware	—	cpe:2.3:o:qualcomm:qcn9024_firmware:-:::::::*
qualcomm	qcs603_firmware	—	cpe:2.3:o:qualcomm:qcs603_firmware:-:::::::*
qualcomm	qcs605_firmware	—	cpe:2.3:o:qualcomm:qcs605_firmware:-:::::::*
qualcomm	qcs6490_firmware	—	cpe:2.3:o:qualcomm:qcs6490_firmware:-:::::::*
qualcomm	qrb5165_firmware	—	cpe:2.3:o:qualcomm:qrb5165_firmware:-:::::::*
qualcomm	qrb5165m_firmware	—	cpe:2.3:o:qualcomm:qrb5165m_firmware:-:::::::*
qualcomm	qrb5165n_firmware	—	cpe:2.3:o:qualcomm:qrb5165n_firmware:-:::::::*
qualcomm	qsm8250_firmware	—	cpe:2.3:o:qualcomm:qsm8250_firmware:-:::::::*
qualcomm	qsm8350_firmware	—	cpe:2.3:o:qualcomm:qsm8350_firmware:-:::::::*
qualcomm	sa6145p_firmware	—	cpe:2.3:o:qualcomm:sa6145p_firmware:-:::::::*
qualcomm	sa6155_firmware	—	cpe:2.3:o:qualcomm:sa6155_firmware:-:::::::*
qualcomm	sa6155p_firmware	—	cpe:2.3:o:qualcomm:sa6155p_firmware:-:::::::*
qualcomm	sa8150p_firmware	—	cpe:2.3:o:qualcomm:sa8150p_firmware:-:::::::*
qualcomm	sa8155_firmware	—	cpe:2.3:o:qualcomm:sa8155_firmware:-:::::::*
qualcomm	sa8155p_firmware	—	cpe:2.3:o:qualcomm:sa8155p_firmware:-:::::::*
qualcomm	sa8295p_firmware	—	cpe:2.3:o:qualcomm:sa8295p_firmware:-:::::::*
qualcomm	sa8540p_firmware	—	cpe:2.3:o:qualcomm:sa8540p_firmware:-:::::::*
qualcomm	sa9000p_firmware	—	cpe:2.3:o:qualcomm:sa9000p_firmware:-:::::::*
qualcomm	sd_675_firmware	—	cpe:2.3:o:qualcomm:sd_675_firmware:-:::::::*
qualcomm	sd_8_gen1_5g_firmware	—	cpe:2.3:o:qualcomm:sd_8_gen1_5g_firmware:-:::::::*
qualcomm	sd_8cx_firmware	—	cpe:2.3:o:qualcomm:sd_8cx_firmware:-:::::::*
qualcomm	sd_8cx_gen2_firmware	—	cpe:2.3:o:qualcomm:sd_8cx_gen2_firmware:-:::::::*
qualcomm	sd_8cx_gen3_firmware	—	cpe:2.3:o:qualcomm:sd_8cx_gen3_firmware:-:::::::*
qualcomm	sd670_firmware	—	cpe:2.3:o:qualcomm:sd670_firmware:-:::::::*
qualcomm	sd675_firmware	—	cpe:2.3:o:qualcomm:sd675_firmware:-:::::::*
qualcomm	sd678_firmware	—	cpe:2.3:o:qualcomm:sd678_firmware:-:::::::*
qualcomm	sd690_5g_firmware	—	cpe:2.3:o:qualcomm:sd690_5g_firmware:-:::::::*
qualcomm	sd750g_firmware	—	cpe:2.3:o:qualcomm:sd750g_firmware:-:::::::*
qualcomm	sd765_firmware	—	cpe:2.3:o:qualcomm:sd765_firmware:-:::::::*
qualcomm	sd765g_firmware	—	cpe:2.3:o:qualcomm:sd765g_firmware:-:::::::*
qualcomm	sd768g_firmware	—	cpe:2.3:o:qualcomm:sd768g_firmware:-:::::::*
qualcomm	sd778g_firmware	—	cpe:2.3:o:qualcomm:sd778g_firmware:-:::::::*
qualcomm	sd780g_firmware	—	cpe:2.3:o:qualcomm:sd780g_firmware:-:::::::*
qualcomm	sd845_firmware	—	cpe:2.3:o:qualcomm:sd845_firmware:-:::::::*
qualcomm	sd850_firmware	—	cpe:2.3:o:qualcomm:sd850_firmware:-:::::::*
qualcomm	sd855_firmware	—	cpe:2.3:o:qualcomm:sd855_firmware:-:::::::*
qualcomm	sd865_5g_firmware	—	cpe:2.3:o:qualcomm:sd865_5g_firmware:-:::::::*
qualcomm	sd870_firmware	—	cpe:2.3:o:qualcomm:sd870_firmware:-:::::::*
qualcomm	sd888_firmware	—	cpe:2.3:o:qualcomm:sd888_firmware:-:::::::*
qualcomm	sd888_5g_firmware	—	cpe:2.3:o:qualcomm:sd888_5g_firmware:-:::::::*
qualcomm	sdx24_firmware	—	cpe:2.3:o:qualcomm:sdx24_firmware:-:::::::*
qualcomm	sdx50m_firmware	—	cpe:2.3:o:qualcomm:sdx50m_firmware:-:::::::*
qualcomm	sdx55_firmware	—	cpe:2.3:o:qualcomm:sdx55_firmware:-:::::::*
qualcomm	sdx55m_firmware	—	cpe:2.3:o:qualcomm:sdx55m_firmware:-:::::::*
qualcomm	sdx57m_firmware	—	cpe:2.3:o:qualcomm:sdx57m_firmware:-:::::::*
qualcomm	sdx65_firmware	—	cpe:2.3:o:qualcomm:sdx65_firmware:-:::::::*
qualcomm	sdx70m_firmware	—	cpe:2.3:o:qualcomm:sdx70m_firmware:-:::::::*
qualcomm	sdxr2_5g_firmware	—	cpe:2.3:o:qualcomm:sdxr2_5g_firmware:-:::::::*
qualcomm	sm7250p_firmware	—	cpe:2.3:o:qualcomm:sm7250p_firmware:-:::::::*
qualcomm	sm7315_firmware	—	cpe:2.3:o:qualcomm:sm7315_firmware:-:::::::*

References for CVE-2022-33232

URL	Tags
https://www.qualcomm.com/company/product-security/bulletins/february-2023-bulletin	Vendor Advisory

URL

CVE-2022-33232 | Buffer copy without checking size of input in Hypervisor

Exploit prediction scoring system (EPSS) score for CVE-2022-33232

Common vulnerability scoring system (CVSS) metrics for CVE-2022-33232

Weakness enumeration for CVE-2022-33232

Affected software / configurations for CVE-2022-33232

References for CVE-2022-33232