LiveActive security incident?Get immediate response
CVE Record

CVE-2000-0338: Concurrent Versions Software (CVS) uses predictable temporary file names for locking, which allows local us...

Concurrent Versions Software (CVS) uses predictable temporary file names for locking, which allows local users to cause a denial of service by creating the lock directory before it is created for use by a legitimate CVS user.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A very old flaw in the CVS source-control tool let anyone with a local user account on the same server block legitimate CVS users from working. By pre-creating a predictably named lock folder, an attacker keeps CVS from acquiring its own lock. It is a nuisance-level denial of service, not data theft or takeover, and only affects users on the same machine. Limited to multi-user systems running a vulnerable CVS build from around 2000 where untrusted local accounts exist. Modern environments using Git or patched/hosted CVS are effectively out of scope. Exposure is negligible for typical enterprises today unless legacy UNIX build hosts still run this era of CVS. Very low priority for modern environments. Only worth attention if legacy CVS servers with shared local accounts remain in production; in that case, fold remediation into planned decommissioning or VCS-migration work rather than emergency patching. Mitigation focus: Upgrade CVS to a modern patched release or migrate the repository to Git or another current VCS.; Restrict shell access on CVS servers to trusted users and enforce least-privilege on lock directories.; Consult vendor or distribution guidance for the specific CVS build in use before applying local fixes..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2000-0338 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.