Search: com.py

Multiple Python packages on PyPI contain legacy bootstrap scripts that create a domain takeover risk. These scripts reference domains that are no longer controlled by the original owners, allowing attackers to register these domains and potentially hijack package functionality or distribution. This vulnerability can lead to supply chain attacks, compromising the integrity and trustworthiness of affected Python packages. No known exploits are currently observed in the wild, but the risk is considered high due to the potential impact on software supply chains. European organizations relying on affected PyPI packages could face significant security risks, including unauthorized code execution and data compromise. Mitigation requires auditing dependencies for legacy bootstrap scripts, removing or updating vulnerable code, and monitoring domain ownership related to package infrastructure. Countries with strong Python developer communities and critical infrastructure relying on Python are most at risk. The threat severity is assessed as high given the ease of exploitation and potential widespread impact on confidentiality, integrity, and availability.

News#infosecnews#redditGermany+7

### Impact An attacker who uses this vulnerability can craft a PDF which leads to a memory usage of up to 1 GB per stream. This requires parsing the content stream of a page using the LZWDecode filter. This is a follow up to [GHSA-jfx9-29x2-rv3j](https://github.com/py-pdf/pypdf/security/advisories/GHSA-jfx9-29x2-rv3j) to align the default limit with the one for *zlib*. ### Patches This has been fixed in [pypdf==6.4.0](https://github.com/py-pdf/pypdf/releases/tag/6.4.0). ### Workarounds If users cannot upgrade yet, use the line below to overwrite the default in their code: ```python pypdf.filters.LZW_MAX_OUTPUT_LENGTH = 75_000_000 ```

CISA has issued a warning about active spyware campaigns targeting high-value users of Signal and WhatsApp messaging platforms. These campaigns aim to hijack accounts and compromise communications through sophisticated spyware infections. The threat actors focus on individuals with sensitive or strategic communications, leveraging vulnerabilities or social engineering to deploy spyware. This poses significant risks to confidentiality and privacy, especially for organizations relying on these encrypted messaging services. European organizations using Signal and WhatsApp for secure communications are at risk of espionage and data theft. The campaigns do not currently have known exploits in the wild but are considered high priority due to their targeted nature and potential impact. Mitigation requires enhanced user awareness, strict device hygiene, and monitoring for suspicious activity. Countries with high adoption of these messaging apps and strategic geopolitical interests are most vulnerable. The severity is assessed as high given the potential for significant confidentiality breaches and the difficulty in detecting spyware infections.

News#infosecnews#redditGermany+9

A Python-based worm propagates through WhatsApp, spreading the Eternidade stealer malware primarily targeting Brazilian devices. This malware harvests sensitive information from infected systems, leveraging social engineering via WhatsApp to self-replicate and infect new victims. Although currently focused on Brazil, the worm's propagation method and malware payload pose risks to any WhatsApp users, including European organizations with employees or contacts linked to Brazil. The worm does not require complex exploits but relies on user interaction to propagate. There is no known CVSS score, but the threat is assessed as high severity due to its potential impact on confidentiality and ease of spread. Defenders should focus on user awareness, endpoint detection, and network monitoring to mitigate infection risks. Countries with strong economic or cultural ties to Brazil and high WhatsApp usage are more likely to be affected in Europe.

Malware#infosecnews#redditPortugal+6

Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * receptor: quic-go Crash Due to Premature HANDSHAKE_DONE Frame (CVE-2025-59530) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: * Python has been updated to 3.11 (AAP-53469) * Nginx has been updated to 1.24 (AAP-53989 and AAP-53990) Refer to Release Notes for details about Python 3.11 update. Automation controller * Added support for Red Hat username and password for the subscription management API (AAP-56887) * Added a step in the subscription wizard that allows the user to configure automation analytics (AAP-56061) * Added two new toggle options on the subscription wizard to allow for fetching subscriptions using basic authentication (AAP-56060) * Fixed an issue in receptor where some edge cases caused JSON to fail to parse (AAP-55917) * Fixed an issue in ansible-runner where there was not a meaningful error message whenever the streaming of logs was aborted * ansible-runner has been updated to 2.3.7 * automation-controller has been updated to 4.5.27 * receptor has been updated to 1.6.2 Installer and setup * Set REDHAT_CANDLEPIN_VERIFY to correct CA pem so that controller can make requests to subscription.rhsm.redhat.com (AAP-57020) * RHEL minimum version has been updated to 8.10 and 9.4 (AAP-56387) * installer and setup have been updated to 2.4-14

The 'SpearSpecter' campaign is a high-severity espionage operation attributed to Iranian threat actors targeting defense and government entities. It involves sophisticated spear-phishing and possibly custom malware to infiltrate sensitive networks. While no specific vulnerabilities or exploits have been publicly disclosed, the campaign's focus on high-value targets indicates a strategic intent to gather intelligence. European defense and government organizations are at risk due to their geopolitical relevance and collaboration with global security partners. The threat actors likely employ stealthy tactics to maintain persistence and evade detection. Mitigation requires enhanced email filtering, network monitoring for anomalous activity, and strict access controls. Countries with significant defense industries and government institutions, such as the UK, Germany, France, and Italy, are most likely to be targeted. Given the campaign's espionage nature, ease of exploitation is moderate but impact on confidentiality is critical. Defenders should prioritize threat intelligence sharing and incident response readiness to counter this evolving threat.

Campaign#infosecnews#redditGermany+9

APT-C-60 continues to target Japan and East Asia with spear-phishing attacks impersonating job seekers. The attack flow has evolved, now directly attaching malicious VHDX files to emails. The malware, including Downloader1, Downloader2, and SpyGlace, has been updated with new features and communication methods. SpyGlace versions 3.1.12, 3.1.13, and 3.1.14 were observed, with changes in Mutex values and execution paths. The attackers use GitHub for payload distribution and employ sophisticated encoding and encryption techniques. The campaign abuses legitimate services and maintains consistent behavioral patterns despite infrastructure changes.

Malware#github#vhdxGermany+6

### Summary An attacker can send a specially crafted POST (multipart/form-data) request. When the aiohttp server processes it, the server will enter an infinite loop and be unable to process any further requests. ### Impact An attacker can stop the application from serving requests after sending a single request. ------- For anyone needing to patch older versions of aiohttp, the minimum diff needed to resolve the issue is (located in `_read_chunk_from_length()`): ```diff diff --git a/aiohttp/multipart.py b/aiohttp/multipart.py index 227be605c..71fc2654a 100644 --- a/aiohttp/multipart.py +++ b/aiohttp/multipart.py @@ -338,6 +338,8 @@ class BodyPartReader: assert self._length is not None, "Content-Length required for chunked read" chunk_size = min(size, self._length - self._read_bytes) chunk = await self._content.read(chunk_size) + if self._content.at_eof(): + self._at_eof = True return chunk async def _read_chunk_from_stream(self, size: int) -> bytes: ``` This does however introduce some very minor issues with handling form data. So, if possible, it would be recommended to also backport the changes in: https://github.com/aio-libs/aiohttp/commit/cebe526b9c34dc3a3da9140409db63014bc4cf19 https://github.com/aio-libs/aiohttp/commit/7eecdff163ccf029fbb1ddc9de4169d4aaeb6597 https://github.com/aio-libs/aiohttp/commit/f21c6f2ca512a026ce7f0f6c6311f62d6a638866

### Summary Security-sensitive parts of the *Python HTTP parser* retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input. ### Details These problems are rooted in pattern matching protocol elements, previously improved by PR #3235 and GHSA-gfw2-4jvh-wgfg: 1. The expression `HTTP/(\d).(\d)` lacked another backslash to clarify that the separator should be a literal dot, not just *any* Unicode code point (result: `HTTP/(\d)\.(\d)`). 2. The HTTP version was permitting Unicode digits, where only ASCII digits are standards-compliant. 3. Distinct regular expressions for validating HTTP Method and Header field names were used - though both should (at least) apply the common restrictions of rfc9110 `token`. ### PoC `GET / HTTP/1ö1` `GET / HTTP/1.𝟙` `GET/: HTTP/1.1` `Content-Encoding?: chunked` ### Impact Primarily concerns running an aiohttp server without llhttp: 1. **behind a proxy**: Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling. 2. **directly accessible** or exposed behind proxies relaying malformed input: the unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities. ----- Patch: https://github.com/aio-libs/aiohttp/pull/8074/files

SleepyDuck is a malicious Visual Studio Code extension (VSX) that leverages the Ethereum blockchain to maintain the availability of its command and control (C2) server, making takedown efforts more difficult. This malware uses decentralized infrastructure to evade traditional detection and disruption methods. Although no known exploits are currently active in the wild, the technique represents an innovative persistence mechanism. The threat targets developers using VS Code extensions, potentially compromising development environments and sensitive code. European organizations relying heavily on VS Code in software development are at risk, especially those in critical infrastructure and technology sectors. Mitigation requires strict extension vetting, network monitoring for unusual blockchain-related traffic, and restricting extension installation policies. Countries with strong software development industries and high VS Code adoption, such as Germany, France, and the UK, are more likely to be affected. Given the medium severity, the threat impacts confidentiality and integrity with moderate exploitation complexity and no user interaction required once installed. Defenders should prioritize detection of unusual extension behavior and blockchain communication patterns to prevent persistent C2 connections.

News#infosecnews#redditGermany+5

A critical Windows zero-day vulnerability is actively exploited by Chinese threat actors to conduct espionage targeting European diplomats. This zero-day allows attackers to compromise Windows systems without requiring user interaction or authentication, enabling stealthy surveillance operations. Although specific affected Windows versions are not detailed, the exploitation focuses on high-value diplomatic targets in Europe. No patches or CVEs have been released yet, and public technical details remain limited. The threat poses significant risks to confidentiality and integrity of sensitive diplomatic communications and data. European organizations, especially government and diplomatic entities, face heightened risk due to the strategic targeting by a nation-state actor. Immediate mitigation requires enhanced monitoring, network segmentation, and strict access controls. Countries with extensive diplomatic presence and geopolitical relevance to China are most likely affected. Given the critical impact and active exploitation, this zero-day vulnerability demands urgent attention and tailored defensive measures.

### Summary While setting up an oauth client, it was noticed that the callback page hosted by the client during the flow embeds user-controlled content without escaping or sanitizing it. This leads to a reflected Cross-Site-Scripting vulnerability. ### Details The affected code is located in *https://github.com/jlowin/fastmcp/blob/main/src/fastmcp/client/oauth_callback.py*, which embeds all values passed to the `create_callback_html` function via the `message` parameter it into the callback page without escaping them. This can, for example, be abused by calling the callback server with an XSS payload inside the `error` GET parameter, the value of which will then be inserted into the callback page, causing the execution of attacker-controlled JavaScript code in the callback server's origin. Note that besides the `error` parameter, other parameters reaching this function are affected too. ### PoC 1. Setup a simple fastmcp client such as this one (the callback server's port was fixated for simplicity): ``` url="http://127.0.0.1:8000/mcp" oauth = OAuth(mcp_url=url,callback_port=1337) async def main(): async with Client(url, auth=oauth) as client: await client.ping() # List available operations tools = await client.list_tools() print(f"tools: {tools}") asyncio.run(main()) ``` 2. Ensure that the MCP server located at `http://127.0.0.1:8000/mcp` supports oauth. 3. Start the client. 4. As soon as the callback server has been started, access `http://localhost:1337/callback?error=<img/src/onerror=alert(window.origin)>` Note that the exploitation could also for example be initiated by a malicious authorization server by returning the exploitation URL mentioned before in the `authorization_endpoint` field. The client would then automatically open, causing the XSS to trigger immediatly. ### Impact The impact of this XSS vulnerability is the arbitrary JavaScript execution in the victim's browser in the callback server's origin.

An Italian spyware vendor has been linked to zero-day attacks targeting the Google Chrome browser. These zero-day vulnerabilities allow attackers to execute malicious code or gain unauthorized access through Chrome, potentially compromising user confidentiality and system integrity. Although no public exploits have been confirmed in the wild yet, the critical severity rating highlights the urgency of addressing this threat. European organizations using Chrome are at risk, especially those in Italy due to proximity and potential targeting. The spyware vendor's involvement suggests a sophisticated threat actor capable of leveraging undisclosed vulnerabilities for espionage or data theft. Defenders should prioritize monitoring for unusual Chrome activity, apply any forthcoming patches immediately, and consider enhanced endpoint detection. Countries with high Chrome usage and strategic value, such as Italy, Germany, France, and the UK, are most likely to be affected. Given the zero-day nature, ease of exploitation is high once the vulnerability is known, and no user interaction may be required. Immediate proactive defense measures are recommended to mitigate potential impact.

Vulnerability#infosecnews#redditItaly+3

### Impact An attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires parsing the content stream of a page using the LZWDecode filter. ### Patches This has been fixed in [pypdf==6.1.3](https://github.com/py-pdf/pypdf/releases/tag/6.1.3). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [#3502](https://github.com/py-pdf/pypdf/pull/3502).

### Impact An attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires parsing the content stream of a page which has an inline image using the DCTDecode filter. ### Patches This has been fixed in [pypdf==6.1.3](https://github.com/py-pdf/pypdf/releases/tag/6.1.3). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [#3501](https://github.com/py-pdf/pypdf/pull/3501).

Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * python3.11-django: Potential partial directory-traversal via archive.extract() (CVE-2025-59682) * automation-gateway: tar-fs symlink validation bypass (CVE-2025-59343) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: Automation Platform * Azure AD authentication now searches more fields to find the username override field specified. If not found it will log a warning message indicating which fields are valid (AAP-53789) * Support TLSv1.3 on server-to-server requests, where previously services which only supported TLSv1.3 would not work (AAP-49456) * Added a step in the subscription wizard that allows the user to configure automation analytics (AAP-55094) * Subscription credentials can no longer be viewed/edited from the system settings page (AAP-55014) * Fixed an issue where the settings displayed "Red Hat" inconsistently in the API and UI (AAP-54277) * Fixed a bug where platform auditors were not able to see Automation Execution and Platform level settings (AAP-53975) * Fixed an issue where some fields were missing the autocomplete = new-password setting (AAP-53934) * Fixed an issue where AAP could not set/create a playbook when using branch override (AAP-52566) * Empty strings are no longer displayed in the extra variables field on the Jobs > Details page (AAP-49448) * Added two new toggle options on the subscription wizard to allow for fetching subscriptions using basic authentication (AAP-47865) * Fixed validation of prompt-on-launch credentials in a workflow job template (AAP-40540) * Fixed an issue for comments in extra vars sections, all comments in YAML are now persisted on create and edit operations for a resource (AAP-37071) * Updated error handling in the Authenticator form to match other forms in the Platform UI (AAP-22928) * automation-gateway has been updated to 2.5.20251022 * automation-gateway-proxy has been updated to 2.5.10-3 for RHEL8 * automation-gateway-proxy has been updated to 2.6.6-4 for RHEL9 * python3.11-django-ansible-base has been updated to 2.5.20251022 Automation controller * Fixed an issue where the ansible.platform collection did not work with the default Red Hat Ansible Automation Platform credential type (AAP-55685) * Fixed an issue in callback receiver and dispatcher crash loop state caused by re-running the installer with modified inventory hostname (AAP-55638) * Added support for Red Hat username and password for the subscription management API (AAP-54976) * Fixes system_administrator role creation race condition which most commonly happened on new openshift deployments resulting in the default instance group not being created (AAP-54964) * Fixed an issue where Grafana notifications couldn't have an empty dashboard ID or panel ID (AAP-54654) * Improved stability on long-running jobs, clusters under heavy load and network flakiness in receptor (AAP-53742) * Fixed Platform Auditor to view controller settings (AAP-53345) * Added missing instruction to set an environment variable in the CLI in order to achieve compatibility with the current release (AAP-37812) * Fixed Platform Auditor to view Metrics API endpoint (AAP-36492) * automation-controller has been updated to 4.6.21 * receptor has been updated to 1.6.0 Automation hub * Fixed an issue where _ui/v2/ user detail displayed the data correctly (AAP-55957) * automation-hub has been updated to 4.10.9 * python3.11-galaxy-ng has been updated to 4.10.9 * python3.11-galaxy-importer has been updated to 0.4.34 Container-based Ansible Automation Platform * Set REDHAT_CANDLEPIN_VERIFY to correct CA pem so that controller can make requests to subscription.rhsm.redhat.com (AAP-55181) * Implemented preflight ansible-core version validation (AAP-54931) * Fixed a bug where Ansible would fail to gather the system's UUID for Linux on Power (AAP-54540) * containerized installer setup has been updated to 2.5-20 RPM-based Ansible Automation Platform * Fixed an issue where setting automationgateway_disable_https=false resulted in install failure (AAP-55475) * Set REDHAT_CANDLEPIN_VERIFY to correct CA pem so that controller can make requests to subscription.rhsm.redhat.com (AAP-55184) * Fixed issue where RESOURCE_KEY SECRET_KEY was not updated when restoring from a different environment (AAP-54944) * Fixed issue where EDA DE credentials fa

A recent high-severity cyberattack involved hackers leveraging Snappybee malware combined with a vulnerability in Citrix products to breach a European telecom network. The attack exploited weaknesses in Citrix infrastructure, allowing malware deployment and unauthorized access. This breach highlights the risk posed by unpatched Citrix vulnerabilities and sophisticated malware targeting critical telecom infrastructure. European telecom operators are at risk of data theft, service disruption, and potential espionage. Mitigation requires immediate patching of Citrix systems, enhanced network segmentation, and advanced malware detection tailored to Snappybee. Countries with significant telecom infrastructure relying on Citrix solutions, such as Germany, France, and the UK, are most likely affected. Given the high impact on confidentiality and availability, ease of exploitation, and critical nature of telecom networks, the threat severity is assessed as high. Defenders must prioritize Citrix patch management and monitor for Snappybee indicators to prevent similar breaches.

Malware#infosecnews#redditGermany+5

The ClickFix analysis highlights the growing threat of copy/paste attacks as a significant driver of security breaches. These attacks exploit the common user behavior of copying and pasting data, often leading to credential theft, injection of malicious commands, or unauthorized data exfiltration. Although no specific software vulnerability or exploit is detailed, the threat emphasizes the human and process weaknesses that facilitate these breaches. European organizations are at risk due to widespread use of affected platforms and the high value of their data. Mitigation requires targeted user training, enhanced endpoint monitoring for clipboard activity, and implementation of strict data handling policies. Countries with advanced digital economies and high adoption of remote work technologies, such as Germany, France, and the UK, are particularly vulnerable. Given the ease of exploitation and potential impact on confidentiality and integrity without requiring sophisticated tools or authentication, the threat severity is assessed as high. Defenders should prioritize awareness campaigns and technical controls to detect and prevent malicious copy/paste activities.

News#infosecnews#redditGermany+6

Certain malicious packages published on popular software repositories npm, PyPI, and RubyGems have been discovered exfiltrating developer data to Discord channels. These packages covertly send sensitive information such as environment variables, source code snippets, or credentials to attacker-controlled Discord servers. The threat affects developers who incorporate these packages into their projects, potentially exposing confidential data and intellectual property. Although no known exploits in the wild have been reported yet, the high severity rating is due to the risk of data leakage and supply chain compromise. This issue highlights the risks inherent in open-source software supply chains and the need for rigorous package vetting. European organizations relying on these ecosystems for software development could face confidentiality breaches and reputational damage. Mitigations include auditing dependencies, using software composition analysis tools, and restricting network egress from development environments. Countries with strong software development sectors and high adoption of these package managers, such as Germany, the UK, France, and the Netherlands, are more likely to be impacted. The threat is assessed as high severity given the potential for significant data exposure without requiring user interaction or authentication. Defenders should prioritize dependency hygiene and monitoring for suspicious outbound traffic from development systems.

News#infosecnews#redditGermany+6

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle