| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in LumoNet PHP Include. This affects an unknown part. Performing a manipulation results in memory corruption. This vulnerability is known as CVE-2014-6236. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in LumoNet PHP Include (Programming Language Software). It has been classified as critical. This affects an unknown functionality. 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 confidentiality, integrity, and availability. The summary by CVE is:
Unspecified vulnerability in the LumoNet PHP Include (lumophpinclude) extension before 1.2.1 for TYPO3 allows remote attackers to execute arbitrary scripts via vectors related to extension links.
The weakness was published 09/11/2014 (Website). The advisory is shared at typo3.org. This vulnerability is uniquely identified as CVE-2014-6236 since 09/04/2014. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 11599 (TYPO3 LumoNet PHP Include Extension SQL Injection Vulnerability (TYPO3-EXT-SA-2014-010)).
Upgrading to version 1.2.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (95707), SecurityFocus (BID 69569†) and Secunia (SA60873†). Similar entries are available at VDB-71210, VDB-71209, VDB-71208 and VDB-71207. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: LumoNet PHP Include 1.2.0
Timeline
09/02/2014 🔍09/04/2014 🔍
09/05/2014 🔍
09/11/2014 🔍
09/11/2014 🔍
03/26/2015 🔍
12/15/2024 🔍
Sources
Advisory: typo3.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2014-6236 (🔍)
GCVE (CVE): GCVE-0-2014-6236
GCVE (VulDB): GCVE-100-71205
X-Force: 95707 - LumoNet PHP Include (lumophpinclude) extension for TYPO3 unspecified code execution
SecurityFocus: 69569 - TYPO3 LumoNet PHP Include Extension Unspecified Arbitrary Code Execution Vulnerability
Secunia: 60873 - TYPO3 LumoNet PHP Include Extension Unspecified Arbitrary Code Execution Vulnerability, Highly Critical
See also: 🔍
Entry
Created: 03/26/2015 15:08Updated: 12/15/2024 02:34
Changes: 03/26/2015 15:08 (52), 03/18/2018 11:06 (7), 12/15/2024 02:34 (18)
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.