← Back to results
Vulnerability record · public intelligence
CVE-2010-4015
UNKNOWN

CVE-2010-4015

Published Feb 2, 2011 · Updated Oct 23, 2026

Severity · CVSSUNKNOWN · 6.5
Known exploitationNot listed
EPSS / likelihood4.62%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Buffer overflow in the gettoken function in contrib/intarray/_int_bool.c in the intarray array module in PostgreSQL 9.0.x before 9.0.3, 8.4.x before 8.4.7, 8.3.x before 8.3.14, and 8.2.x before 8.2.20 allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via integers with a large number of digits to unspecified functions.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Buffer overflow in the gettoken function in contrib/intarray/_int_bool.c in the intarray array module in PostgreSQL 9.0.x before 9.0.3, 8.4.x before 8.4.7, 8.3.x before 8.3.14, and 8.2.x before 8.2.20 allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via integers with a large number of digits to unspecified functions.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. ADV-2011-0283 ↗
  2. 70740 ↗
  3. 43144 ↗
  4. HPSBMU02781 ↗
  5. RHSA-2011:0198 ↗
  6. FEDORA-2011-0990 ↗
  7. RHSA-2011:0197 ↗
  8. www.postgresql.org ↗
  9. ADV-2011-0349 ↗
  10. 43187 ↗
  11. SUSE-SR:2011:005 ↗
  12. USN-1058-1 ↗

Record history

Published Feb 2, 2011 · Last refreshed Oct 23, 2026