dbcve.org
Suse LinuxOperating system · Suse

CVE-2002-0854

HIGH · 7.2 CVSS v2.0 Published 2002-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer overflows in ISDN Point to Point Protocol (PPP) daemon (ipppd) in the i4l package on SuSE 7.3, 8.0, and possibly other operating systems, may allow local users to gain privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Buffer overflow vulnerability in the ISDN Point to Point Protocol daemon (ipppd) within the i4l package allows local unprivileged users to potentially execute arbitrary code and gain root privileges by exploiting insufficient bounds checking in the daemon.

MitigationApply SuSE security patches for the i4l package; if patches are unavailable, upgrade to a supported SuSE version or restrict local shell access to trusted users only until a fix can be deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Suse LinuxOperating system
Affected:= 7.3= 8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Suse Linux version
    Run 'cat /etc/SuSE-release' or 'lsb_release -a' to determine the exact version number
    Affected if The version is 7.3 or 8.0
  2. Verify the i4l package is installed
    Check for the i4l package using the package manager: 'rpm -qa | grep i4l' or 'dpkg -l | grep i4l'
    Affected if The i4l package is present on the system
  3. Confirm the ipppd daemon exists
    Check for the ipppd binary: 'which ipppd' or 'ls -la /usr/sbin/ipppd'
    Affected if The ipppd binary is present on the system
  4. Determine if ISDN support is configured
    Check for ISDN configuration files in /etc/isdn/ or run 'isdnctrl list' to see active ISDN interfaces
    Affected if ISDN interfaces are configured or the ipppd daemon is actively handling ISDN connections

The system is affected if it is running Suse Linux 7.3 or 8.0 with the i4l package installed and the ipppd daemon present, particularly if ISDN is configured or in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SuSE security patches for the i4l package; if patches are unavailable, upgrade to a supported SuSE version or restrict local shell access to trusted users only until a fix can be deployed.

Fix this in Suse Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-0854 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-0854 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data