Security readout for executives and security teams
This PostgreSQL flaw can let a logged-in database user infer common values from columns they may query, even when row-level security should hide some rows. It is a limited confidentiality issue, not a system takeover. The main concern is multi-tenant or role-separated databases using row-level security. Exposure is most likely where PostgreSQL row-level security protects sensitive rows and lower-privileged roles still have SELECT on the relevant columns. Systems not using row-level security, or not running the listed vulnerable versions, are unlikely to be affected by this CVE. Treat this as a targeted privacy and tenant-isolation risk, not an emergency remote compromise. Patch through normal database maintenance, but prioritize any PostgreSQL systems that rely on row-level security to separate customers, departments, or restricted records. Mitigation focus: Upgrade PostgreSQL to 11.3, 10.8, 9.6.13, 9.5.17, or later supported releases.; Follow PostgreSQL and operating-system vendor advisories for packaged update instructions.; Prioritize databases using row-level security for tenant, customer, or role separation..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-10130 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.1 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N1.61.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
3.1LowVector: CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.postgresql.org/about/news/1939/CVE reference · x_refsource_MISC
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10130CVE reference · x_refsource_CONFIRM
- GLSA-202003-03CVE reference · vendor-advisory, x_refsource_GENTOO
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.