SecPod

Learn Search

Search across all Learn content

← Back to Security Research
Same Origin Method Execution (SOME) Vulnerability

Same Origin Method Execution (SOME) Vulnerability

A new vulnerability has been discovered by Ben Hayak, a researcher at Trustwave, at Black Hat Europe in Amsterdam, that can gain access into your private cloud and steal information like private photos, video albums, etc., just by clicking on a malicious link. This attack happens before the user rea...

May 31, 2016By Tushar K3 min read
(Source: benhayak.com)
(Source: benhayak.com)

A new vulnerability has been discovered by Ben Hayak, a researcher at Trustwave, at Black Hat Europe in Amsterdam, that can gain access into your private cloud and steal information like private photos, video albums, etc., just by clicking on a malicious link. This attack happens before the user realizes that something is going wrong. Yes, that means the application is vulnerable to a new attack called Same Origin Method Execution (SOME). A good Vulnerability Management Tool can resolve these issues.

Same Origin Method Execution is a web application attack related to JavaScript Object Notation with padding (JSONP) implementation that allows an attacker to perform unlimited unintended actions on a website on behalf of users. Vulnerability Management Software is the solution to prevent these attacks.

Unlike many other similar attacks, there is no need for user interaction if malicious advertising (malvertising) is in use as a vector. In fact, when a web page is vulnerable to the Same Origin Method Execution, the entire domain becomes exposed to its resulting vulnerabilities.

How the attack works:

  1. The victim clicks on the malicious link.
  2. A new window is opening for each of the methods that are in execution.
  3. The application then allows the vulnerable callback URL to render the document targeting by the attack and is quick, so the victim has no idea what is occurring.
  4. The application is ‘tricked’ into thinking both sites are trustworthy, and the application can now be hijacked into thinking the end user is doing all actions.

Same Origin Policy (SOP) is a fundamental security mechanism that prevents unrelated websites from interacting with each other.  This mechanism restricts vulnerable websites from running javascript that they don’t have permission. However, sometimes, there are situations where a website needs to communicate with third-party services by overcoming the Same Origin Policy.

Consider the example that a website that needs to identify its visitor’s location might use a geolocation service such as Telize. In this case, Web developers can use JSONP, a communication technique that allows websites to request data from servers in a different domain by taking advantage of the fact that browsers don’t enforce SOP on <script> tags.

While JSONP is a popular and useful technology, it can make a website vulnerable if not implemented properly. JSONP uses a callback function to get data from third-party services. The attacker could execute arbitrary methods on the affected website by manipulating the callback parameter.

According to the researcher, an attacker can execute as many methods as necessary. However, Many popular domains like Google, Yahoo, and Microsoft, along with applications like WordPress and VideoJS,  affecting by the Same Origin Method Execution Vulnerability, which was working correctly.

Primary reasons to affect websites by SOME vulnerability

According to the researcher, there are possibly four reasons which SOME vulnerabilities can affect websites:

  1. If the application requires “secure delegated access” to third-party server resources like OAuth.
  2. If the application opens a pop-up window, it does not lose the current content on the display.
  3. If the application developers use a simpler yet unsecure SOP bypass.
  4. If developers simply lack security awareness.

Ways to secure Websites against SOME attack

However, according to the researcher, there are only three ways to secure websites from SOME attack that uses JSONP implementation:

  1. Use a static function name for all callback endpoints.
  2. Whitelist callbacks on the server side.
  3. Registering callbacks.

Featured Posts

Open CVE-2026-31431: From 732 Bytes to Root - Anatomy of a Modern Linux Privilege Escalation

CVE-2026-31431: From 732 Bytes to Root - Anatomy of a Modern Linux Privilege Escalation

CVE Research

CVE-2026-31431: From 732 Bytes to Root - Anatomy of a Modern Linux Privilege Escalation

Jun 24, 2026

Open CVE-2026-31431: The Nine-Year Kernel Bug Hiding in Plain Sight

CVE-2026-31431: The Nine-Year Kernel Bug Hiding in Plain Sight

CVE Research

CVE-2026-31431: The Nine-Year Kernel Bug Hiding in Plain Sight

Jun 23, 2026

Open Squidbleed: A 29-Year-Old Squid Proxy Flaw That Leaks Cleartext HTTP Requests
Squidbleed: A 29-Year-Old Squid Proxy Flaw That Leaks Cleartext HTTP Requests

CVE Research

Squidbleed: A 29-Year-Old Squid Proxy Flaw That Leaks Cleartext HTTP Requests

Jun 23, 2026

Open AryStinger Malware Leverages 4,300+ Legacy Routers to Establish Persistent Spy Infrastructure
AryStinger Malware Leverages 4,300+ Legacy Routers to Establish Persistent Spy Infrastructure

CVE Research

AryStinger Malware Leverages 4,300+ Legacy Routers to Establish Persistent Spy Infrastructure

AryStinger represents a calculated shift in IoT threat methodology, abandoning noisy, destructive payloads in favor of silent, long-term reconnaissance infrastructure. By exploiting unpatched, end-of-life routers and NAS devices through decade-old vulnerabilities, the threat operator has assembled a distributed fleet of over 4,300 Executor nodes capable of conducting parallelized DNS enumeration, port scanning, and service fingerprinting at scale, all while masking origin behind residential IP addresses. With active development ongoing and a potential operational timeline stretching back to 2024, AryStinger underscores a growing and underappreciated risk: forgotten edge hardware is not merely a compliance gap but exploitable infrastructure.

Jun 23, 2026

Same Origin Method Execution (SOME) Vulnerability | SecPod