Humming Heads Defense Platform Home Edition up to 3.9.51.x buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Humming Heads Defense Platform Home Edition up to 3.9.51.x. This issue affects some unknown processing. Performing a manipulation results in buffer overflow. This vulnerability is reported as CVE-2025-23236. The attack requires a local approach. No exploit exists.
Details
A vulnerability was found in Humming Heads Defense Platform Home Edition up to 3.9.51.x. It has been classified as critical. This affects an unknown code. The manipulation with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow vulnerability exists in Defense Platform Home Edition Ver.3.9.51.x and earlier. If an attacker performs a specific operation, SYSTEM privilege of the Windows system where the product is running may be obtained.
The advisory is shared at hummingheads.co.jp. This vulnerability is uniquely identified as CVE-2025-23236 since 01/27/2025. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/04/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 3.9.0
- 3.9.1
- 3.9.2
- 3.9.3
- 3.9.4
- 3.9.5
- 3.9.6
- 3.9.7
- 3.9.8
- 3.9.9
- 3.9.10
- 3.9.11
- 3.9.12
- 3.9.13
- 3.9.14
- 3.9.15
- 3.9.16
- 3.9.17
- 3.9.18
- 3.9.19
- 3.9.20
- 3.9.21
- 3.9.22
- 3.9.23
- 3.9.24
- 3.9.25
- 3.9.26
- 3.9.27
- 3.9.28
- 3.9.29
- 3.9.30
- 3.9.31
- 3.9.32
- 3.9.33
- 3.9.34
- 3.9.35
- 3.9.36
- 3.9.37
- 3.9.38
- 3.9.39
- 3.9.40
- 3.9.41
- 3.9.42
- 3.9.43
- 3.9.44
- 3.9.45
- 3.9.46
- 3.9.47
- 3.9.48
- 3.9.49
- 3.9.50
- 3.9.51
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.3
VulDB Base Score: 7.8
VulDB Temp Score: 7.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (jpcert): 🔍
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: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
01/27/2025 🔍02/06/2025 🔍
02/06/2025 🔍
02/04/2026 🔍
Sources
Advisory: hummingheads.co.jpStatus: Confirmed
CVE: CVE-2025-23236 (🔍)
GCVE (CVE): GCVE-0-2025-23236
GCVE (VulDB): GCVE-100-294837
Entry
Created: 02/06/2025 09:04Updated: 02/04/2026 23:47
Changes: 02/06/2025 09:04 (61), 02/04/2026 23:47 (1)
Complete: 🔍
Cache ID: 216::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.