CVE-1999-1338
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 · uneditedDelegate proxy 5.9.3 and earlier creates files and directories in the DGROOT with world-writable permissions.
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 confidenceDelegate proxy version 5.9.3 and earlier creates files and directories in its DGROOT directory with world-writable permissions (mode 0777), allowing any local user to read, modify, or delete these 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<= 5.9.3CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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.
-
Check if Delegate proxy is installedRun 'delegate -V' or 'which delegate' to locate the Delegate executableAffected if Delegate is present on the system
-
Determine the installed Delegate versionExecute 'delegate -V' and note the version numberAffected if Version is 5.9.3 or earlier
-
Locate the DGROOT directoryCheck Delegate configuration files or run 'delegate -v' to display the DGROOT path, or inspect environment variables if DGROOT is setAffected if A DGROOT directory is defined and accessible
-
Inspect file permissions in DGROOTRun 'ls -la' on the DGROOT directory and examine the permission bits on files and subdirectoriesAffected if Any file or directory shows permissions as 0777 (rwxrwxrwx)
-
Verify ownership allows other users accessCompare the owner of DGROOT files to other local user accounts, confirming other users can read/write/delete due to world-writable bitsAffected if Files are world-writable and other users exist on the system
A system is affected if Delegate version 5.9.3 or earlier is installed with a DGROOT containing files or directories set to mode 0777, allowing any local user to access them.
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 dataRestrict permissions on DGROOT files and directories to owner-only (e.g., umask 077 or explicit chmod 600/700) or upgrade to a patched version if available.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1338 — 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-1999-1338 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