LinuxOperating system · Redhat
CVE-1999-1335
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 · uneditedsnmpd server in cmu-snmp SNMP package before 3.3-1 in Red Hat Linux 4.0 is configured to allow remote attackers to read and write sensitive information.
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 · moderate confidenceThe snmpd server in the cmu-snmp package (versions before 3.3-1) on Red Hat Linux 4.0 was configured with default community strings accessible from remote locations, allowing unauthenticated attackers to read and potentially write sensitive system information via SNMP queries.
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
<= 4.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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Identify if cmu-snmp package is installedCheck for the presence of the cmu-snmp package using the package manager, such as 'rpm -qa | grep cmu-snmp' or 'dpkg -l | grep cmu-snmp' depending on the systemAffected if The cmu-snmp package is installed and no patched version is available
-
Determine the installed snmpd versionRun 'rpm -q cmu-snmp' or check the package version through your system's package management tool to compare against the vulnerable version range (before 3.3-1)Affected if The installed version is earlier than 3.3-1
-
Verify if snmpd service is runningCheck for running snmpd processes using 'ps aux | grep snmpd' or check the service statusAffected if The snmpd daemon is actively running and listening for network requests
-
Inspect community string configurationExamine the snmpd configuration file (commonly /etc/snmp/snmpd.conf) for community string definitions, specifically looking for 'public' or 'private' strings used as read/write community namesAffected if The default community strings 'public' or 'private' are configured without IP-based access restrictions
-
Check for remote access exposureReview snmpd configuration for directives that allow access from any address (0.0.0.0, ::, or no explicit 'community' restriction to localhost only)Affected if SNMP community strings are accessible from remote IP addresses rather than restricted to localhost (127.0.0.1) only
A user is affected if cmu-snmp version below 3.3-1 is installed, the snmpd service is running, and default community strings ('public'/'private') are accessible from remote locations without IP 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 dataConfigure snmpd to restrict community string access to authorized IP addresses only, change default community strings from 'public'/'private' to unique values, and consider upgrading to a supported SNMP implementation.
Fix this in Linux
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1335 — 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-1335 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