VDB
MGASA-2020-0365
MGASA-2020-0365
PUBLISHED
CVSS 8.399999618530273 HIGH
Record from OSV · Published September 6, 2020
Updated postgresql packages fix security vulnerabilities
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| postgresql9.6 | Mageia:7 | 9.6.19-1.mga7 |
| postgresql11 | Mageia:7 | 11.9-1.mga7 |
Risk scores
CVSS 4.0
8.399999618530273
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Mageia:7 | postgresql9.6 | 0 |
| Mageia:7 | postgresql11 | 0 |
Timeline
- Sep 6, 2020 CVE Published
- Apr 16, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln MGASA-2020-0365
vulnetix vdb fixes MGASA-2020-0365Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/MGASA-2020-0365/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart