CVE-2002-1397
Overview
CVE-2002-1397 is a known-severity vulnerability affecting postgresql postgresql. It was published on January 17, 2003.
Technical Description
Vulnerability in the cash_words() function for PostgreSQL 7.2 and earlier allows local users to cause a denial of service and possibly execute arbitrary code via a large negative argument, possibly triggering an integer signedness error or buffer overflow.
Remediation
Check the references section for vendor advisories and patches from postgresql. Update postgresql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|
References
Frequently Asked Questions
What is CVE-2002-1397?
CVE-2002-1397 is a known-severity vulnerability affecting postgresql postgresql. It was published on January 17, 2003.
How severe is CVE-2002-1397?
CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.
How do I fix or remediate CVE-2002-1397?
Check the references section for vendor advisories and patches from postgresql. Update postgresql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2002-1397?
CyberStrike's AI-powered security agents can automatically detect CVE-2002-1397 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.