CVE-1999-1546
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 · uneditednetstation.navio-com.rte 1.1.0.1 configuration script for Navio NC on IBM AIX exports /tmp over NFS as world-readable and world-writable.
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 netstation.navio-com.rte 1.1.0.1 configuration script for Navio NC on IBM AIX configures NFS to export the /tmp directory with world-readable and world-writable permissions, allowing any NFS client on the network to read and write to the exported filesystem.
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= 1.1.0.1CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 Navio NC Browser is installedRun 'lslpp -l netstation.navio-com.rte' or 'rpm -qa | grep navio' on AIX to see if the package is installedAffected if The package netstation.navio-com.rte version 1.1.0.1 is installed on the system
-
Verify NFS is running and exports existRun 'exportfs' or check '/etc/exports' to see current NFS export configurationAffected if NFS exports are configured and /tmp appears in the export list
-
Inspect /tmp export permissionsRun 'exportfs -v' to see detailed export options including access permissions for /tmpAffected if The /tmp export shows no host restrictions (world-accessible) or explicitly shows world-read/write permissions (e.g., -access=*:root or similar unrestricted settings)
-
Confirm world-writable status on /tmp exportReview the /etc/exports file or 'exportfs' output; look for entries like '/tmp -rw,root_squash' or unrestricted exports without specific host limitingAffected if /tmp is exported without restricting access to specific authorized hosts, making it accessible to any NFS client on the network
A system is affected if the netstation.navio-com.rte 1.1.0.1 package is installed and the /tmp directory is exported via NFS without host-based access restrictions.
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 or restrict the NFS export of /tmp in /etc/exports (or via exportfs), restricting access to specific authorized hosts rather than exposing it globally; if this legacy package is still in use, consider whether it is still necessary.
- 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-1546 — 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-1546 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