| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Bro up to 2.3.1. The affected element is an unknown function of the file analyzer/protocol/dnp3/DNP3.cc of the component DNP3 Packet Handler. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2015-1521. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Bro up to 2.3.1. It has been classified as problematic. This affects some unknown processing of the file analyzer/protocol/dnp3/DNP3.cc of the component DNP3 Packet Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on availability. The summary by CVE is:
analyzer/protocol/dnp3/DNP3.cc in Bro before 2.3.2 does not properly handle zero values of a packet length, which allows remote attackers to cause a denial of service (buffer overflow or buffer over-read if NDEBUG; otherwise assertion failure) via a crafted DNP3 packet.
The bug was discovered 01/24/2015. The weakness was released 04/24/2017 (GitHub Repository). It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2015-1521 since 02/06/2015. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 821 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.3.2 eliminates this vulnerability.
Entry connected to this vulnerability is available at VDB-100492. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/bro/bro/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Bro 2.3.2
Patch: github.com
Timeline
01/24/2015 🔍02/06/2015 🔍
04/24/2017 🔍
04/24/2017 🔍
04/24/2017 🔍
12/02/2022 🔍
Sources
Product: github.comAdvisory: 6cedd67c381ff22fde653adf02ee31caf66c81a0
Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-1521 (🔍)
GCVE (CVE): GCVE-0-2015-1521
GCVE (VulDB): GCVE-100-100491
OSVDB: - CVE-2015-1521 - Bro - Buffer Overflow Issue
See also: 🔍
Entry
Created: 04/24/2017 14:41Updated: 12/02/2022 08:38
Changes: 04/24/2017 14:41 (60), 09/20/2020 11:23 (3), 12/02/2022 08:38 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.