D-Link DIR-825 2.10b02 HTTP Request /vct_wan strchr memory corruption

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.9 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in D-Link DIR-825 2.10b02 and classified as critical. This issue affects the function strchr
of the file /vct_wan of the component HTTP Request Handler. The manipulation leads to memory corruption.
The identification of this vulnerability is CVE-2021-29296. The attack may be initiated remotely. There is no exploit available.
Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability has been found in D-Link DIR-825 2.10b02 (Router Operating System) and classified as critical. This vulnerability affects the function strchr
of the file /vct_wan of the component HTTP Request Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. CVE summarizes:
Null Pointer Dereference vulnerability in D-Link DIR-825 2.10b02, which could let a remote malicious user cause a denial of service. The vulnerability could be triggered by sending an HTTP request with URL /vct_wan; the sbin/httpd would invoke the strchr function and take NULL as a first argument, which finally leads to the segmentation fault. NOTE: The DIR-825 and all hardware revisions is considered End of Life and as such this issue will not be patched
The weakness was shared 08/11/2021 as SAP10212. The advisory is shared for download at supportannouncement.us.dlink.com. This vulnerability was named CVE-2021-29296. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/05/2024).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
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: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/29/2021 🔍08/11/2021 🔍
08/11/2021 🔍
06/05/2024 🔍
Sources
Vendor: dlink.comAdvisory: SAP10212
Status: Confirmed
CVE: CVE-2021-29296 (🔍)
GCVE (CVE): GCVE-0-2021-29296
GCVE (VulDB): GCVE-100-180544
Entry
Created: 08/11/2021 12:50 PMUpdated: 06/05/2024 01:24 PM
Changes: 08/11/2021 12:50 PM (40), 08/15/2021 04:00 PM (2), 06/05/2024 11:36 AM (33), 06/05/2024 01:24 PM (3)
Complete: 🔍
Cache ID: 18:5E1:40
No comments yet. Languages: en.
Please log in to comment.