UNKNOWN CVSS 4.6
Published: 2002-04-22

CVE-2002-0175

avaya libsafe Security Advisory (CVE-2002-0175)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2002-0175?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2002-0175 impacting avaya libsafe. Evaluated with CVSS Base Score of 4.6 (UNKNOWN).

Original NVD Description

Source: NIST NVD
libsafe 2.0-11 and earlier allows attackers to bypass protection against format string vulnerabilities via format strings that use the "'" and "I" characters, which are implemented in libc but not libsafe.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Local (AV:L)
Requires local system execution permissions
Attack Complexity
Low (AC:L)
No specialized conditions required

🎯 Affected Versions Matrix

Affected Product avaya / libsafe
Affected Versions 1.3.4
Weakness Enumeration NVD-CWE-Other

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2002-0175 impacting avaya libsafe.

⚡ Nuclei Detection Template (YAML) cve-2002-0175.yaml
id: cve-2002-0175

info:
  name: avaya libsafe - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: unknown
  description: |
    Automated signature & scanner for CVE-2002-0175 affecting avaya libsafe.
    Evaluation: libsafe 2.0-11 and earlier allows attackers to bypass protection against format string vulnerabilities via format strings that use the "'&qu...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2002-0175
  classification:
    cvss-metrics: CVSS:3.1/AV:L/AC:L/Au:N/C:P/I:P/A:P
    cvss-score: 4.6
    cve-id: CVE-2002-0175
    cwe-id: NVD-CWE-Other
  tags: cve,cve-2002-0175,avaya,libsafe,unknown

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "libsafe"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2002-0175.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2002-0175
# Target: avaya libsafe | CVSS: 4.6 (UNKNOWN)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2002-0175 (avaya libsafe)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against avaya libsafe scope (1.3.4).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2002-0175.sh
# Recommended Remediation & Patching Commands for CVE-2002-0175
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install libsafe 2>/dev/null || \
sudo dnf upgrade libsafe 2>/dev/null || \
sudo yum update libsafe

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i libsafe 2>/dev/null || rpm -qa | grep -i libsafe

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2002-0175 in avaya libsafe?

Review vendor-specific security notices and update avaya libsafe packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2002-0175?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2002-0175?

CVE-2002-0175 is classified with a CVSS 3.1 Base Score of 4.6 (UNKNOWN). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
4.6
UNKNOWN SEVERITY
CVE ID CVE-2002-0175
Weakness NVD-CWE-Other
Vendor avaya
Product libsafe
Published 2002-04-22
Vector AV:L/AC:L/Au:N/C:P/I:P/A:P