CVE-2020-21469

What it is

An issue was discovered in PostgreSQL 12.2 allows attackers to cause a denial of service via repeatedly sending SIGHUP signals. NOTE: this is disputed by the vendor because untrusted users cannot send SIGHUP signals; they can only be sent by a PostgreSQL superuser, a user with pg_reload_conf access, or a user with sufficient privileges at the OS level (the postgres account or the root account).

At a glance

Exploitability

Can be exploited locally on the machine with an admin-level account. High risk of service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-08-22 19:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:03 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 4.4 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-08-22 19:16 UTC

Last modified

2026-06-17 03:03 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-120 · Classic buffer overflow

Record status

Modified

Affected

• PostgreSQL 12.2

Attack profile CVSS 3.1 · 4.4

Attack vector

Local

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-21469.md and follow it. Check whether this project is affected by CVE-2020-21469. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge