Samsung Galaxy Store Bug Could’ve Let Hackers Secretly Install Apps on Targeted Devices

Oct 31, 2022

A now-patched security flaw has been disclosed in the Galaxy
Store app for Samsung devices that could potentially trigger remote
command execution on affected phones.

The vulnerability, which affects Galaxy Store version 4.5.32.4,
relates to a cross-site scripting (XSS) bug that occurs when
handling certain deep links ^[1]. An independent security
researcher has been credited with reporting the issue.

“Here, by not checking the deep link securely, when a user
accesses a link from a website containing the deeplink, the
attacker can execute JS code in the webview context of the Galaxy
Store application,” SSD Secure Disclosure said ^[2]
in an advisory posted last week.

XSS attacks ^[3]
allow an adversary to inject and execute malicious JavaScript code
when visiting a website from a browser or another application.

The issue identified in the Galaxy Store app has to do with how
deep links are configured for Samsung’s Marketing & Content Service
(MCS ^[4]), potentially leading to
a scenario where arbitrary code injected into the MCS website could
lead to its execution.

This could then be leveraged to download and install
malware-laced apps on the Samsung device when visiting the
link.

“To be able to successfully exploit the victim’s server, it is
necessary to have HTTPS and CORS bypass of chrome,” the researchers
noted.

References

^{^}
deep
links (developer.android.com)
^{^}
said
(ssd-disclosure.com)
^{^}
XSS
attacks (owasp.org)
^{^}
MCS
(us-mktg.mcsvc.samsung.com)

The Hacker News Headlines

NoFilter Attack: Sneaky Privilege Escalation Method Bypasses Windows Security

Aug 18, 2023

The Hacker News Headlines

Google Chrome’s New Feature Alerts Users About Auto-Removal of Malicious Extensions

Aug 18, 2023

The Hacker News Headlines

New Apple iOS 16 Exploit Enables Stealthy Cellular Access Under Fake Airplane Mode

Aug 18, 2023

OWASP TOP !0

Injection. Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization. Broken Authentication. Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently. Sensitive Data Exposure. Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser. XML External Entities (XXE). Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks. Broken Access Control. Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc. Security Misconfiguration. Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched/upgraded in a timely fashion. Cross-Site Scripting XSS. XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites. Insecure Deserialization. Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks. Using Components with Known Vulnerabilities. Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts. Insufficient Logging & Monitoring. Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.

Samsung Galaxy Store Bug Could’ve Let Hackers Secretly Install Apps on Targeted Devices

References

Related Post

NoFilter Attack: Sneaky Privilege Escalation Method Bypasses Windows Security

Google Chrome’s New Feature Alerts Users About Auto-Removal of Malicious Extensions

New Apple iOS 16 Exploit Enables Stealthy Cellular Access Under Fake Airplane Mode

You missed

Protected: Rotary VI EAST

Protected: BetterCyberCareer Group

Protected: Benin Club 1931 – Official

Protected: Whatsapp AI Automation Group