LinuxOperating system · Corel
CVE-2000-0048
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 · uneditedget_it program in Corel Linux Update allows local users to gain root access by specifying an alternate PATH for the cp program.
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 confidenceThe get_it program in Corel Linux Update executes the cp command without specifying an absolute path, allowing local users to manipulate the PATH environment variable to point to a malicious cp binary. Since get_it runs with elevated privileges as part of the update mechanism, this enables local privilege escalation to root.
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
= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Corel Linux versionCheck the installed OS version by running 'cat /etc/corel-release' or 'cat /etc/redhat-release' and look for 'Corel Linux' version 1.0Affected if The system is running Corel Linux version 1.0
-
Locate the get_it binarySearch for the get_it executable using 'find / -name get_it -type f 2>/dev/null' or check common update utility paths like /usr/bin/get_it, /usr/sbin/get_it, or /sbin/get_itAffected if The get_it binary exists on the system
-
Check for setuid permissionsRun 'ls -la /path/to/get_it' (replace with actual path) and examine the permission bits. Look for 's' in the owner execute field (e.g., -rwsr-xr-x)Affected if The get_it binary has the setuid bit set, indicated by an 's' in the owner permissions and runs as root or another privileged user
-
Verify PATH-based command executionUse 'strings /path/to/get_it' or 'cat /path/to/get_it' (if it is a script) and search for 'cp' commands that are invoked without a leading slash (e.g., 'cp' rather than '/bin/cp')Affected if The get_it binary calls 'cp' without an absolute path, making it vulnerable to PATH manipulation
The system is affected if it is running Corel Linux 1.0 with the get_it binary present, having setuid permissions, and executing the cp command without an absolute path, allowing a local attacker to escalate privileges to root.
Generated from the published advisory. Verify against your own configuration.
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 dataRemove the setuid bit from the get_it binary or rewrite it to use absolute paths for all system commands (e.g., /bin/cp instead of cp), then verify the update functionality remains functional.
Fix this in Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0048 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2000-0048 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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