Beck IPC IPC@CHIP Embedded-Webserver chipcfg.cgi information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Beck IPC IPC@CHIP Embedded-Webserver. It has been classified as problematic. The affected element is an unknown function of the file chipcfg.cgi. This manipulation causes information disclosure. This vulnerability appears as CVE-2001-1341. In addition, an exploit is available. It is advisable to implement restrictive firewalling.
Details
A vulnerability was found in Beck IPC IPC@CHIP Embedded-Webserver (Web Server) (unknown version). It has been declared as problematic. Affected by this vulnerability is an unknown code block of the file chipcfg.cgi. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
The Beck GmbH IPC@Chip embedded web server installs the chipcfg.cgi program by default, which allows remote attackers to obtain sensitive network information via a request to the program.
The weakness was presented 05/24/2001 as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. This vulnerability is known as CVE-2001-1341. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
Proper firewalling of is able to address this issue. Attack attempts may be identified with Snort ID 2116.
The vulnerability is also documented in the databases at X-Force (6600), Exploit-DB (41671) and SecurityFocus (BID 2767†). See VDB-16695, VDB-16692, VDB-16691 and VDB-16689 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.3
VulDB Temp Score: 4.9
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Snort ID: 2116
Snort Message: SERVER-WEBAPP chipcfg.cgi access
Snort Class: 🔍
Timeline
05/24/2001 🔍05/24/2001 🔍
05/24/2001 🔍
07/04/2014 🔍
06/14/2024 🔍
Sources
Advisory: kb.cert.orgStatus: Confirmed
CVE: CVE-2001-1341 (🔍)
GCVE (CVE): GCVE-0-2001-1341
GCVE (VulDB): GCVE-100-16693
CERT: 🔍
X-Force: 6600
SecurityFocus: 2767 - Beck IPC GmbH IPC@CHIP Network Information Disclosure Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 07/04/2014 11:11Updated: 06/14/2024 07:27
Changes: 07/04/2014 11:11 (57), 04/08/2019 09:11 (3), 06/14/2024 03:26 (17), 06/14/2024 07:27 (2)
Complete: 🔍
Cache ID: 216:B14:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.