3Com HiPer Arcs Community Name Vulnerability
BID:537
Info
3Com HiPer Arcs Community Name Vulnerability
| Bugtraq ID: | 537 |
| Class: | Design Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Jul 23 1999 12:00AM |
| Updated: | Jul 23 1999 12:00AM |
| Credit: | First posted to BugTraq by Jeff Mcadams <[email protected]> on July 20, 1999. Some of the solution taken directly from Jeff's BugTraq posting. Update on version numbers provided by zotbot <[email protected]> |
| Vulnerable: |
3Com HiPer Arc 4.1 3Com HiPer Arc 4.0 |
| Not Vulnerable: |
3Com HiPer Arc 5.0 3Com HiPer Arc 4.2 |
Discussion
3Com HiPer Arcs Community Name Vulnerability
On 3Com HiPer Arc cards (and possibly others using the Pilgrim source base), it is possible to gain administrative snmp privileges remotely if you have a valid community string (of any access level). There are three levels of access in the card, read-only, read-write and administrative. The community strings are readable to all levels and makes it possible for an attacker to gain administrative privileges (needing only to view the community string in the usrSnmpCommAccess table and others like it). With administrative access, the attacker can perform a number of malicious activities possibly leading to further compromise (ie, repopulating the arp cache).
This bug existed in ALL HARC 4.0.XX code releases and HARC 4.1.YY releases where YY<59. All HARC code releases after 9/1/99 contain a fix for this issue (this includes all current service releases of HARC 4.1 code and all currently shipping code versions).
Later HARC code versions 4.2.XX as well as 5.0.XX do not contain this problem.
On 3Com HiPer Arc cards (and possibly others using the Pilgrim source base), it is possible to gain administrative snmp privileges remotely if you have a valid community string (of any access level). There are three levels of access in the card, read-only, read-write and administrative. The community strings are readable to all levels and makes it possible for an attacker to gain administrative privileges (needing only to view the community string in the usrSnmpCommAccess table and others like it). With administrative access, the attacker can perform a number of malicious activities possibly leading to further compromise (ie, repopulating the arp cache).
This bug existed in ALL HARC 4.0.XX code releases and HARC 4.1.YY releases where YY<59. All HARC code releases after 9/1/99 contain a fix for this issue (this includes all current service releases of HARC 4.1 code and all currently shipping code versions).
Later HARC code versions 4.2.XX as well as 5.0.XX do not contain this problem.
Exploit / POC
3Com HiPer Arcs Community Name Vulnerability
See Discussion.
See Discussion.
References
3Com HiPer Arcs Community Name Vulnerability
References:
References: