dbcve.org
LinuxOperating system · Redhat

CVE-2000-0355

HIGH · 7.5 CVSS v2.0 Published 1999-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
pg and pb in SuSE pbpg 1.x package allows an attacker to read arbitrary files.

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

The pg and pb command-line utilities in the SuSE pbpg 1.x package contain a path traversal vulnerability that allows authenticated attackers to read arbitrary files on the system by using directory traversal sequences (e.g., ../../../) in file path arguments.

MitigationIdentify and remove or update the vulnerable pbpg package on affected SuSE systems; if the utility is still required, apply any available vendor patches or upgrade to a patched version.

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
LinuxOperating system
Affected:= 6.0
PbpgOperating system
Affected:= 1.1
Suse LinuxOperating system
Affected:= 6.2

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
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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. Check if pbpg package is installed
    On RPM-based systems (Red Hat, SuSE), run: rpm -qa | grep -i pbpg
    Affected if The package 'pbpg' or 'pbpg-*' appears in the query results, indicating the package is installed
  2. Identify installed pbpg version
    Run: rpm -q pbpg --queryformat '%{VERSION}-%{RELEASE}' or check package details via package manager
    Affected if Version equals '1.1' (Bent Bagger) or matches affected Linux distribution versions (6.0 for Red Hat, 6.2 for SuSE)
  3. Verify pg and pb commands exist
    Run: which pg && which pb or ls -la /usr/bin/pg /usr/bin/pb
    Affected if Either command exists and points to the pbpg utility binaries
  4. Confirm path traversal risk
    Check if the utility accepts file path arguments and review any existing wrappers or scripts around pg/pb commands
    Affected if The utility can accept arbitrary file path arguments and no input sanitization is applied

User is affected if the pbpg package (version 1.1 for Bent Bagger, 6.0 for Red Hat, or 6.2 for SuSE) is installed and the pg/pb command-line utilities are present and accessible to authenticated users.

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

Identify and remove or update the vulnerable pbpg package on affected SuSE systems; if the utility is still required, apply any available vendor patches or upgrade to a patched version.

Fix this in Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2000-0355 — 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-2000-0355 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