CVE-1999-1513
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 · uneditedManagement information base (MIB) for a 3Com SuperStack II hub running software version 2.10 contains an object identifier (.1.3.6.1.4.1.43.10.4.2) that is accessible by a read-only community string, but lists the entire table of community strings, which could allow attackers to conduct unauthorized activities.
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 3Com SuperStack II hub (v2.10) has a MIB object (.1.3.6.1.4.1.43.10.4.2) accessible via a read-only SNMP community string that inadvertently exposes the entire table of community strings, allowing attackers to obtain full administrative credentials.
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= 2.10CVSS 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
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 the device modelCheck the device or its management interface for the exact model name - look for '3Com SuperStack II Hub' in the device identification or web interface.Affected if The device is a 3Com SuperStack II Hub.
-
Check the firmware versionAccess the device's management interface or console and retrieve the firmware/software version information.Affected if The version is exactly 2.10.
-
Verify SNMP is enabledCheck the device's configuration for SNMP settings - look for SNMP agent or community string configuration options.Affected if SNMP is enabled and at least one community string is configured.
-
Confirm read-only SNMP accessIdentify whether a read-only (public default) community string is configured on the device.Affected if A read-only community string is set.
-
Query the vulnerable MIB OIDUse an SNMP client (such as snmpwalk or snmpget) with the read-only community string to query the OID .1.3.6.1.4.1.43.10.4.2 - this is the 3Com specific OID that exposes community strings.Affected if The query returns community string data or table entries, exposing administrative credentials.
If the device is a 3Com SuperStack II Hub running version 2.10 with SNMP enabled and a read-only community string, and querying OID .1.3.6.1.4.1.43.10.4.2 returns community string data, the environment is affected by this vulnerability.
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 dataChange all SNMP community strings to strong, unique values not accessible via read-only access; restrict SNMP management to authorized IP addresses; consider replacing this legacy hardware as it may be beyond vendor support.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.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 $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1513 — 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-1513 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