Symantec Security Information Manager prior 4.7.0 Management Console sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Symantec Security Information Manager. Affected is an unknown function of the component Management Console. Performing a manipulation results in sql injection. This vulnerability is reported as CVE-2013-1613. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in Symantec Security Information Manager. It has been classified as critical. This affects some unknown functionality of the component Management Console. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in the management console (aka Java console) on the Symantec Security Information Manager (SSIM) appliance 4.7.x and 4.8.x before 4.8.1 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.
The weakness was disclosed 07/08/2013 (Website). The advisory is shared at symantec.com. This vulnerability is uniquely identified as CVE-2013-1613 since 02/04/2013. The exploitability is told to be easy. The attack can only be initiated within the local network. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 4.7.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 60796†). The entries VDB-64439 and VDB-64438 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.symantec.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.5
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
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: 🔍
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: Security Information Manager 4.7.0
Timeline
02/04/2013 🔍07/01/2013 🔍
07/08/2013 🔍
07/08/2013 🔍
03/24/2015 🔍
02/12/2018 🔍
Sources
Vendor: symantec.comAdvisory: symantec.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2013-1613 (🔍)
GCVE (CVE): GCVE-0-2013-1613
GCVE (VulDB): GCVE-100-64437
SecurityFocus: 60796 - Symantec Security Information Manager CVE-2013-1613 SQL Injection Vulnerability
See also: 🔍
Entry
Created: 03/24/2015 15:54Updated: 02/12/2018 08:06
Changes: 03/24/2015 15:54 (47), 02/12/2018 08:06 (6)
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.