GaussDB 200 with version of 6.5.1 have a command injection vulnerability.

published 2020-02-17 6y ago modified 2026-06-17 4mo ago also EUVD-2020-12637

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

GaussDB 200 with version of 6.5.1 have a command injection vulnerability. Due to insufficient input validation, remote attackers with low permissions could exploit this vulnerability by sending crafted commands to the affected device. Successful exploit could allow an attacker to execute commands.

Is CVE-2020-1811 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 Fencer

Exploit prediction

1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

Huawei GaussDB 200

Classification

Weakness

CWE-20 Improper Input Validation
CWE-77 Improper Neutralization of Special Elements used in a Command

References

huawei.com /en/psirt/security-advisories/huawei-sa-20200120-01-gaussdb200-en
vendor-advisory

Sources

CVE List CVE-2020-1811
NVD CVE-2020-1811

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.