CVE-2020-4271 json
IBM QRadar 7.3.0 to 7.3.3 Patch 2 could allow an authenticated user to send a specially crafted command which would be executed as a lower…
published 6y ago modified 4mo ago also EUVD-2020-25518
- cvss
- 6.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
IBM QRadar 7.3.0 to 7.3.3 Patch 2 could allow an authenticated user to send a specially crafted command which would be executed as a lower privileged user. IBM X-ForceID: 175897.
Patch / fix
- ibm qradar_security_information_and_event_manager 7.3.3
Is CVE-2020-4271 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.73% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/157336/QRadar-Community-Edition-7.3.1.6-PHP-Object-Injection.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.3 | CVSS:3.0/I:L/A:L/S:U/C:L/UI:N/AV:N/AC:L/PR:L/RC:C/RL:O/E:U |
| NVD | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.0 | 6.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- IBM Qradar
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
packetstormsecurity.com
/files/157336/QRadar-Community-Edition-7.3.1.6-PHP-Object-Injection.html
exploit, third-party-advisory, vdb-entry
-
ibm.com
/support/pages/node/6189651
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/175897
vdb-entry, vendor-advisory
-
seclists.org
/fulldisclosure/2020/Apr/39
mailing-list, third-party-advisory
Sources
- CVE List CVE-2020-4271
- NVD CVE-2020-4271
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.