dbcve.org
LinuxOperating system · Corel

CVE-2000-0195

HIGH · 7.2 CVSS v2.0 Published 2000-02-24
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
setxconf in Corel Linux allows local users to gain root access via the -T parameter, which executes the user's .xserverrc file.

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 setxconf utility in Corel Linux accepts a -T parameter that executes the user's .xserverrc file with root privileges. A local attacker can place arbitrary commands in their ~/.xserverrc file, which will be executed with elevated privileges when setxconf runs with the -T flag, achieving local privilege escalation.

MitigationRemove the setxconf binary from the system or ensure it does not have SUID root permissions. If the application is still required, remove or sanitize the -T parameter functionality to prevent execution of user-controlled files.

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:= 1.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. Check if setxconf binary exists
    Run: which setxconf or find /usr -name setxconf 2>/dev/null
    Affected if The binary is present on the system
  2. Check setxconf file permissions
    Run: ls -la /path/to/setxconf (replace with actual path from step 1)
    Affected if The file has SUID root permissions (rwsr-xr-x or -rwSr--r--) or is owned by root with execute permissions for others
  3. Verify -T parameter functionality
    Run setxconf --help or setxconf -h to check if -T parameter is recognized
    Affected if The -T parameter is available and documented or visible in usage output
  4. Check for user-writable .xserverrc
    Check if ~/.xserverrc exists and is writable: ls -la ~/.xserverrc
    Affected if A .xserverrc file exists in a user's home directory and can be modified by that user

A user is affected if the setxconf binary exists, has SUID root permissions, and supports the -T parameter, allowing arbitrary code execution via a user-controlled ~/.xserverrc file.

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

Remove the setxconf binary from the system or ensure it does not have SUID root permissions. If the application is still required, remove or sanitize the -T parameter functionality to prevent execution of user-controlled files.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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