| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in jCore 1.0. This impacts an unknown function of the component rlogin. This manipulation causes sql injection. This vulnerability is handled as CVE-2012-4232. The attack can be initiated remotely. Additionally, an exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical was found in jCore 1.0. Affected by this vulnerability is an unknown code of the component rlogin. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in admin/index.php in jCore before 1.0pre2 allows remote attackers to execute arbitrary SQL commands via the memberloginid cookie.
The weakness was released 10/22/2012 with High-Tech Bridge Security Research Lab (Website). It is possible to read the advisory at jcore.net. This vulnerability is known as CVE-2012-4232 since 08/09/2012. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
It is possible to download the exploit at packetstormsecurity.com. It is declared as proof-of-concept.
Upgrading to version 1.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (79442) and SecurityFocus (BID 56102†). Entry connected to this vulnerability is available at VDB-62730. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: jCore 1.0
Timeline
08/09/2012 🔍10/17/2012 🔍
10/22/2012 🔍
10/22/2012 🔍
03/24/2015 🔍
06/15/2024 🔍
Sources
Advisory: jcore.netOrganization: High-Tech Bridge Security Research Lab
Status: Not defined
Confirmation: 🔍
CVE: CVE-2012-4232 (🔍)
GCVE (CVE): GCVE-0-2012-4232
GCVE (VulDB): GCVE-100-62731
X-Force: 79442
SecurityFocus: 56102 - jCore SQL Injection and Cross Site Scripting Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/24/2015 12:22Updated: 06/15/2024 21:26
Changes: 03/24/2015 12:22 (54), 02/23/2019 08:42 (1), 06/15/2024 21:26 (24)
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.