CVE-1999-1245 in ucd-snmp
Summary
by MITRE
vacm ucd-snmp SNMP server, version 3.52, does not properly disable access to the public community string, which could allow remote attackers to obtain sensitive information.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 04/19/2026
The vulnerability identified as CVE-1999-1245 affects the ucd-snmp SNMP server version 3.52, specifically within the View-Based Access Control Model implementation. This represents a critical security flaw in network management protocols that has persisted for over two decades, highlighting the long-term impact of inadequate access control mechanisms in SNMP implementations. The vulnerability stems from improper configuration of the public community string, which serves as a fundamental authentication mechanism in SNMP versions 1 and 2c. When this community string remains enabled and accessible, it provides unauthorized parties with direct access to network device information and configuration data.
The technical flaw manifests in the vacm component of ucd-snmp, which is responsible for managing access control policies within the SNMP framework. This component fails to properly disable or restrict access to the default public community string, allowing remote attackers to bypass authentication mechanisms entirely. The vulnerability specifically impacts SNMPv1 and SNMPv2c implementations where community strings function as passwords for accessing network information. Attackers can exploit this weakness by simply sending an SNMP GET request to the target server using the public community string, thereby retrieving sensitive information such as system information, network configuration details, interface statistics, and potentially confidential data stored on managed devices.
The operational impact of this vulnerability extends beyond simple information disclosure, as it provides attackers with comprehensive access to network infrastructure details that can be leveraged for further attacks. Network administrators who fail to properly configure their SNMP servers may unknowingly expose critical infrastructure information to remote threat actors. This vulnerability directly relates to CWE-284, which addresses improper access control in software systems, and aligns with ATT&CK technique T1046 for network service scanning and T1082 for system information discovery. The exposure of sensitive data through this vulnerability can facilitate more sophisticated attacks including privilege escalation, lateral movement, and comprehensive network reconnaissance that could compromise entire network infrastructures.
Mitigation strategies for CVE-1999-1245 require immediate administrative action to disable or change the public community string configuration. System administrators must ensure that the public community string is either completely disabled or replaced with a strong, non-default value that is properly secured and restricted. The recommended approach involves configuring the SNMP server to disable the public view or implementing proper access control lists that restrict community string usage. Organizations should also implement network segmentation and firewall rules to limit access to SNMP ports, typically UDP port 161, from trusted networks only. Additionally, migrating to SNMPv3 implementations is strongly advised as this version provides robust authentication and encryption mechanisms that eliminate the vulnerabilities present in earlier SNMP versions. Regular security audits and vulnerability assessments should be conducted to ensure that SNMP configurations remain secure and that no unauthorized access points exist within network management systems.