LiveActive security incident?Get immediate response
CVE Record

CVE-2010-1975: PostgreSQL 7.4 before 7.4.29, 8.0 before 8.0.25, 8.1 before 8.1.21, 8.2 before 8.2.17, 8.3 before 8.3.11, a...

PostgreSQL 7.4 before 7.4.29, 8.0 before 8.0.25, 8.1 before 8.1.21, 8.2 before 8.2.17, 8.3 before 8.3.11, and 8.4 before 8.4.4 does not properly check privileges during certain RESET ALL operations, which allows remote authenticated users to remove arbitrary parameter settings via a (1) ALTER USER or (2) ALTER DATABASE statement.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old PostgreSQL privilege-checking flaw. An authenticated remote database user could remove parameter settings through certain RESET ALL behavior tied to ALTER USER or ALTER DATABASE. The risk is mainly for legacy PostgreSQL deployments or products bundling those versions, not current supported PostgreSQL releases. Exposure is most likely in unsupported legacy PostgreSQL servers, old Linux distribution packages, or appliances embedding PostgreSQL from the affected branches. Modern supported PostgreSQL deployments are unlikely to be affected unless they retain these historic versions or vendor backports without the relevant fix. Prioritize this when legacy PostgreSQL exists in production or regulated environments. The flaw requires authentication, but it can undermine database configuration controls. If no affected legacy versions are present, this should be tracked as a hygiene and asset-discovery item rather than an emergency. Mitigation focus: Upgrade PostgreSQL to the fixed version for the affected branch or a supported current release.; Apply distribution vendor updates such as Debian DSA-2051 where package-managed PostgreSQL is used.; Identify products or appliances bundling PostgreSQL 7.4 through 8.4-era builds..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2010-1975 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.