LiveActive security incident?Get immediate response
CVE Record

CVE-2001-1379: The PostgreSQL authentication modules (1) mod_auth_pgsql 0.9.5, and (2) mod_auth_pgsql_sys 0.9.4, allow rem...

The PostgreSQL authentication modules (1) mod_auth_pgsql 0.9.5, and (2) mod_auth_pgsql_sys 0.9.4, allow remote attackers to bypass authentication and execute arbitrary SQL via a SQL injection attack on the user name.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2001-1379 affects old PostgreSQL authentication modules for Apache: mod_auth_pgsql 0.9.5 and mod_auth_pgsql_sys 0.9.4. A remote attacker could bypass authentication and run arbitrary SQL by abusing username handling. This is a legacy issue, but it matters if these modules still protect web resources or connect to sensitive databases.

Executive priority

Treat as high priority only if the affected legacy modules are present. The potential business impact is serious because authentication controls and database integrity may be compromised. If not present, document non-exposure and monitor for legacy reintroduction.

Technical view

The vulnerability is described as SQL injection in the username field of mod_auth_pgsql 0.9.5 and mod_auth_pgsql_sys 0.9.4. Reported impacts are authentication bypass and arbitrary SQL execution. The source bundle does not provide CVSS, CWE, patch details, or affected CPE data.

Likely exposure

Likely limited to legacy Apache deployments using mod_auth_pgsql 0.9.5 or mod_auth_pgsql_sys 0.9.4 for PostgreSQL-backed authentication. Modern environments are exposed only if these modules remain installed, enabled, and reachable.

Exploitation context

No CISA KEV entry is indicated, and the provided sources do not state active exploitation. The vulnerability is remotely reachable where the affected authentication module processes usernames for protected resources.

Researcher notes

Evidence is sparse and old. The CVE record names specific versions and impact but provides no patch metadata, CVSS, or exploit-status confirmation. Avoid assuming broader product exposure beyond the two named modules and versions.

Mitigation direction

  • Inventory Apache modules and identify any mod_auth_pgsql or mod_auth_pgsql_sys usage.
  • If affected versions are present, remove, disable, or replace the legacy authentication module.
  • Check vendor or project guidance for fixed versions or migration recommendations.
  • Review database account privileges used by the authentication module.
  • Restrict exposure to protected endpoints until remediation is complete.

Validation and detection

  • Confirm whether Apache loads mod_auth_pgsql or mod_auth_pgsql_sys.
  • Record exact module versions from package metadata or build records.
  • Identify web locations relying on PostgreSQL-backed authentication.
  • Review logs for unusual authentication failures or database errors involving usernames.
  • Verify database credentials used by the module have least privilege.
Prepared
Confidence
medium
Sources
3

Public sources used

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-2001-1379 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.