Avaya Argent Office 2.1 SNMP Service Community Name improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Avaya Argent Office 2.1. Affected by this vulnerability is an unknown functionality of the component SNMP Service. Such manipulation of the argument Community Name leads to improper authentication. This vulnerability is listed as CVE-2001-1262. In addition, an exploit is available. Restrictive firewalling should be applied.
Details
A vulnerability, which was classified as critical, has been found in Avaya Argent Office 2.1. Affected by this issue is some unknown functionality of the component SNMP Service. The manipulation of the argument Community Name with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Avaya Argent Office 2.1 compares a user-provided SNMP community string with the correct string only up to the length of the user-provided string, which allows remote attackers to bypass authentication with a 0 length community string.
The weakness was presented 08/07/2001 as not defined posting (Bugtraq). The advisory is available at online.securityfocus.com. This vulnerability is handled as CVE-2001-1262. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.
It is declared as proof-of-concept.
Addressing this vulnerability is possible by firewalling udp/161 (snmp).
The vulnerability is also documented in the databases at X-Force (6955) and SecurityFocus (BID 8974†). See VDB-17135, VDB-17136 and VDB-17137 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.avaya.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.7
VulDB Base Score: 7.3
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Firewalling: 🔍
Timeline
08/07/2001 🔍08/07/2001 🔍
08/07/2001 🔍
07/07/2014 🔍
04/08/2019 🔍
Sources
Vendor: avaya.comAdvisory: online.securityfocus.com⛔
Status: Not defined
CVE: CVE-2001-1262 (🔍)
GCVE (CVE): GCVE-0-2001-1262
GCVE (VulDB): GCVE-100-17138
X-Force: 6955 - Argent Office allows network user to obtain community string
SecurityFocus: 8974 - Avaya Argent Office SNMP Authentication Mechanism Weaknesses
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 07/07/2014 17:30Updated: 04/08/2019 16:34
Changes: 07/07/2014 17:30 (58), 04/08/2019 16:34 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.