Samsung Samsung Security Manager up to 1.29 access control

Summaryinfo

A vulnerability classified as problematic has been found in Samsung Samsung Security Manager up to 1.29. The impacted element is an unknown function of the component Manager. The manipulation leads to access control. This vulnerability is listed as CVE-2015-1499. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Samsung Samsung Security Manager up to 1.29. It has been rated as critical. This issue affects some unknown processing of the component Manager. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is integrity, and availability. The summary by CVE is:

The ActiveMQ Broker in Samsung Security Manager (SSM) before 1.31 allows remote attackers to delete arbitrary files, and consequently cause a denial of service, via a DELETE request.

The weakness was presented 02/16/2015 (Website). The advisory is shared at xforce.iss.net. The identification of this vulnerability is CVE-2015-1499 since 02/05/2015. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 1.30 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at X-Force (100918). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Samsung

Name

• Samsung Security Manager

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29

License

• commercial

Website

• Vendor: https://www.samsung.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion