Search: development.we

Tuleap is an Open Source Suite for management of software development and collaboration. Tuleap Community Edition versions below 17.0.99.1762444754 and Tuleap Enterprise Edition versions prior to 17.0-2, 16.13-7 and 16.12-10 allow attackers trick victims into changing tracker general settings. This issue is fixed in version Tuleap Community Edition version 17.0.99.1762444754 and Tuleap Enterprise Edition versions 17.0-2, 16.13-7 and 16.12-10.

Tuleap is an Open Source Suite for management of software development and collaboration. Versions below 17.0.99.1762431347 of Tuleap Community Edition and Tuleap Enterprise Edition below 17.0-2, 16.13-7 and 16.12-10 allow attackers to access file release system information in projects they do not have access to. This issue is fixed in version 17.0.99.1762431347 of the Tuleap Community Edition and versions 17.0-2, 16.13-7 and 16.12-10 of Tuleap Enterprise Edition.

China-linked threat actors rapidly weaponized the React2Shell vulnerability shortly after its public disclosure, indicating a swift exploitation attempt in the wild. React2Shell is a critical remote code execution vulnerability affecting systems that use the React framework or related components. Although no confirmed exploits in the wild have been reported yet, the speed of weaponization suggests imminent risk. European organizations using vulnerable React-based applications or AWS services could face unauthorized code execution, leading to data breaches, service disruption, or lateral movement within networks. Mitigation requires immediate patching, monitoring for suspicious activity, and restricting access to vulnerable services. Countries with significant cloud adoption and software development sectors, such as Germany, the UK, France, and the Netherlands, are at higher risk. Given the ease of exploitation and potential impact on confidentiality, integrity, and availability, this threat is assessed as high severity. Defenders should prioritize rapid vulnerability management and threat hunting to prevent compromise.

News#infosecnews#redditGermany+6

A recent analysis reveals that malicious Visual Studio Code (VS Code) extensions can bypass the official VS Code Marketplace's security analysis, exploiting weaknesses in both the Marketplace and the OpenVSX alternative. Attackers can publish extensions that appear legitimate but contain harmful code, potentially compromising developer environments. This threat highlights the insecurity of OpenVSX, an open-source VS Code extension registry, which lacks rigorous vetting processes. European organizations relying on VS Code and OpenVSX for development tools face risks of code injection, data leakage, and supply chain attacks. Mitigations include strict extension source verification, enhanced monitoring of extension behavior, and restricting extension installation to trusted repositories. Countries with strong software development sectors and high VS Code adoption, such as Germany, France, and the UK, are particularly at risk. Given the ease of exploitation without authentication and the potential impact on confidentiality and integrity, this threat is assessed as high severity. Defenders should prioritize vetting extensions, educating developers, and employing endpoint protection to mitigate risks.

Tool#netsec#redditGermany+6

In the Linux kernel, the following vulnerability has been resolved: btrfs: ensure no dirty metadata is written back for an fs with errors [BUG] During development of a minor feature (make sure all btrfs_bio::end_io() is called in task context), I noticed a crash in generic/388, where metadata writes triggered new works after btrfs_stop_all_workers(). It turns out that it can even happen without any code modification, just using RAID5 for metadata and the same workload from generic/388 is going to trigger the use-after-free. [CAUSE] If btrfs hits an error, the fs is marked as error, no new transaction is allowed thus metadata is in a frozen state. But there are some metadata modifications before that error, and they are still in the btree inode page cache. Since there will be no real transaction commit, all those dirty folios are just kept as is in the page cache, and they can not be invalidated by invalidate_inode_pages2() call inside close_ctree(), because they are dirty. And finally after btrfs_stop_all_workers(), we call iput() on btree inode, which triggers writeback of those dirty metadata. And if the fs is using RAID56 metadata, this will trigger RMW and queue new works into rmw_workers, which is already stopped, causing warning from queue_work() and use-after-free. [FIX] Add a special handling for write_one_eb(), that if the fs is already in an error state, immediately mark the bbio as failure, instead of really submitting them. Then during close_ctree(), iput() will just discard all those dirty tree blocks without really writing them back, thus no more new jobs for already stopped-and-freed workqueues. The extra discard in write_one_eb() also acts as an extra safenet. E.g. the transaction abort is triggered by some extent/free space tree corruptions, and since extent/free space tree is already corrupted some tree blocks may be allocated where they shouldn't be (overwriting existing tree blocks). In that case writing them back will further corrupting the fs.

ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In 5.5.1, 5.4.3, 5.3.4, 5.2.6, 5.1.6, and earlier, when AVRCP is enabled on ESP32, receiving a malformed VENDOR DEPENDENT command from a peer device can cause the Bluetooth stack to access memory before validating the command buffer length. This may lead to an out-of-bounds read, potentially exposing unintended memory content or causing unexpected behavior.

North Korean (NK) hackers have distributed approximately 200 malicious npm packages containing the OtterCookie malware. These packages were uploaded to the npm repository, a popular package manager for JavaScript, potentially targeting developers and organizations relying on npm dependencies. OtterCookie malware is designed to stealthily compromise systems, potentially enabling data exfiltration or further malicious activity. Although no known exploits in the wild have been reported yet, the scale and nature of the campaign pose a significant risk. European organizations using npm packages in their software supply chain could be exposed to this threat, especially if they do not have strict dependency vetting processes. Mitigation requires enhanced supply chain security measures, including automated scanning of dependencies, restricting use of unverified packages, and continuous monitoring for anomalous behavior. Countries with strong software development sectors and high npm usage, such as Germany, the UK, France, and the Netherlands, are particularly at risk. Given the malware’s potential for confidentiality breaches and the ease of exploitation via package installation, the threat severity is assessed as high. Defenders should prioritize verifying package integrity and implementing zero-trust principles in software supply chains to mitigate this threat.

Malware#infosecnews#redditGermany+6

The Water Saci campaign is a sophisticated malware operation primarily targeting Brazilian banking and cryptocurrency platforms via WhatsApp. It employs multi-format malware delivery using various scripting languages, including a shift from PowerShell to Python, likely enhanced by AI tools to evade detection and complicate analysis. The malware features aggressive anti-sandbox techniques, extensive backdoor capabilities, and persistence mechanisms. Although currently focused on Brazil, the use of WhatsApp as a propagation vector and targeting financial applications poses a potential risk to European organizations with ties to Brazilian markets or users. The campaign’s complexity and AI-enhanced development pipeline indicate a medium severity threat with significant evasion and persistence capabilities. Defenders should prioritize monitoring WhatsApp-based phishing attempts, scrutinize multi-format file attachments, and implement advanced behavioral detection to mitigate risks. Countries with strong economic or diaspora links to Brazil and high WhatsApp usage are more likely to be affected.

Malware#backdoor#pythonPortugal+6

CVE-2025-41086 is a medium-severity vulnerability in AMS Development Corp. 's GAMS software licensing system. It involves an authorization bypass through a user-controlled key due to an insecure checksum algorithm used in license validation. Attackers can generate unlimited valid licenses without credentials or source code access, granting unrestricted use of GAMS's mathematical models and commercial solvers. The vulnerability requires no authentication or user interaction and can be exploited remotely. Although no known exploits are currently reported in the wild, the flaw poses significant risks to organizations relying on GAMS for critical mathematical and optimization tasks. European organizations using GAMS may face unauthorized usage and intellectual property theft. Mitigation requires AMS to update the licensing validation mechanism with a secure cryptographic approach and for users to monitor license usage closely. Countries with strong industrial, academic, and research sectors using GAMS are most likely affected.

An unauthenticated attacker can trick a local user into executing arbitrary code by opening a deliberately manipulated CODESYS project file with a CODESYS development system. This arbitrary code is executed in the user context.

This update for gimp fixes the following issues: Changes in gimp: Update to 3.0.6: - Security: - During development, we received reports from the Zero Day Initiative of potential security issues with some of our file import plug-ins. While these issues are very unlikely to occur with real files, developers like Jacob Boerema and Alx Sa proactively improved security for those imports. The resolved reports are: - ZDI-CAN-27793 - ZDI-CAN-27823 - ZDI-CAN-27836 - ZDI-CAN-27878 - ZDI-CAN-27863 - ZDI-CAN-27684 - Core: - Many false-positive build warnings have been cleaned out (and proper issues fixed). - Various crashes fixed. - When creating a layer mask from the layer's alpha, but the layer has no alpha, simply fill the mask with complete opacity instead of a completely transparent layer. - Various core infrastructure code reviewed, cleaned up, refactored and improved, in drawable, layer and filter handling code, tree view code, and more. - GIMP_ICONS_LIKE_A_BOSS environment variable is not working anymore (because "gtk-menu-images" and "gtk-button-images" have been deprecated in GTK3 and removed in GTK4) and was therefore removed. - Lock Content now shows as an undo step. - Add alpha channel for certain transforms. - Add alpha channel on filter merge, when necessary. - Filters can now be applied non-destructively on channels. - Improved Photoshop brush support. - After deleting a palette entry, the next entry is automatically selected. This allows easily deleting several entries in a row, among other usage. - Resize image to layers irrespective to selections. - Improved in-GUI release notes' demo script language: - We can now set a button value to click it: "toolbox:text, tool-options:outline=1, tool-options:outline-direction" - Color selector's module names can be used as identifiers: "color-editor,color-editor:CMYK=1,color-editor:total-ink-coverage" - Fixed Alpha to Selection on single layers with no transparency. - Various code is slowly ported to newer code, preparing for GTK4 port (in an unplanned future step): - Using g_set_str() (optionally redefining it in our core code to avoid bumping the GLib minimum requirement). - Start using GListModel in various pieces of code, in particular getting rid of more and more usage of GtkTreeView when possible (as it will be deprecated with GTK4). - New GimpRow class for all future row widgets. - Use more of G_DECLARE_DERIVABLE_TYPE and G_DECLARE_FINAL_TYPE where relevant. - New GimpContainerListView using a GtkListBox. - New GimpRowSeparator, GimpRowSettings, GimpRowFilter and GimpRowDrawableFilter widgets. - (Experimental) GEX Format was updated. - Palette import: - Set alpha value for image palette imports. - Fix Lab & CMYK ACB palette import. - Add palette format filters to import dialog, making it more apparent what palette formats are supported, and giving the ability to hide irrelevant files. - Improved filter actions' sensitivity to make sure they are set insensitive when relevant. In particular filters which cannot be run non-destructively (e.g. filters with aux inputs, non-interactive filters and GEGL Graph) must be insensitive when trying to run them on group layers. - Fix bad axis centering on zoom out. - Export better SVG when exporting paths. - Tools: - Text tool: make sure the default color is only changed when the user confirms the color change. - Foreground Selection tool: do not create a selection when no strokes has been made. In particular this removes the unnecessary delay which happened when switching to another tool without actually stroking anything. - All Transform tools: transform boundaries for preview is now multi-layers aware. - (Experimental) Seamless Clone tool: made to work again, though it is still too slow to get out of Playground. - Graphical User Interface: - Various improvements to window management: - Keep-Above windows are set with the Utility hint. - Utility windows are not made transient to a parent. - Transient factory dialogs follow the active display, ensuring that new image windows would not hide your toolbox and dock windows. - Various CSS improvements for styling of the interface. Some theme leaks were also fixed. - New toggle button in Brushes and Fonts dockable, allowing brush and font previews to optionally follow the color theme. For instance, when using a dark theme, the brush and font previews could be drawn on the theme background, using the theme foreground colors. By default, th

Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses the User-Agent header starting with the string "Mozilla" as a defense mechanism. This defense is insufficient as the fetch specification allows the User-Agent header to be modified. Combined with a DNS rebinding attack against the browser, and this vulnerability is exploitable against a developer running Ray who inadvertently visits a malicious website, or is served a malicious advertisement (malvertising). This issue has been patched in version 2.52.0.

A recently disclosed edge case vulnerability affects the mysql and mysql2 Node.js packages, where prepared statements—commonly trusted to prevent SQL injection—can be exploited under certain conditions. This vulnerability undermines the assumption that using prepared statements alone guarantees SQL injection safety, potentially allowing attackers to execute arbitrary SQL commands. While no known exploits are currently in the wild, the issue poses a medium severity risk due to its impact on data confidentiality and integrity. European organizations using Node.js applications with these database libraries should carefully review their usage of prepared statements and apply mitigations promptly. Countries with significant Node.js development ecosystems and industries relying on web applications and databases are at higher risk. Mitigation involves auditing code for unsafe prepared statement usage, applying any forthcoming patches, and employing additional input validation and query parameterization techniques. Given the ease of exploitation once the vulnerability is understood and the widespread use of these packages, the threat demands immediate attention despite limited current exploitation evidence.

News#netsec#redditGermany+6

Palo Alto Networks has conducted an analysis of malicious LLMs that help threat actors with phishing, malware development, and reconnaissance. The post WormGPT 4 and KawaiiGPT: New Dark LLMs Boost Cybercrime Automation appeared first on SecurityWeek .

PhishingGermanyFrance+5

CVE-2025-29933 is a medium severity vulnerability in AMD μProf caused by improper input validation leading to an out-of-bounds write. This flaw allows a local attacker with limited privileges to write outside intended memory bounds, potentially causing application crashes or denial of service. The vulnerability does not impact confidentiality or integrity but affects availability. Exploitation requires local access and no user interaction, limiting remote attack feasibility. No known exploits are currently reported in the wild. European organizations using AMD μProf for performance profiling on AMD processors may be affected, especially in sectors relying on AMD hardware for development or performance analysis. Mitigations include restricting local access to AMD μProf, applying vendor patches when available, and monitoring for abnormal application behavior. Countries with significant AMD hardware adoption and strong tech sectors, such as Germany, France, and the UK, are more likely to be impacted. Overall, this vulnerability poses a moderate risk primarily through denial of service scenarios in local environments.

EPSS 0.1%VulnerabilityCWE-787Germany+2

The Chinese AI model DeepSeek-R1 has been found to generate insecure code specifically when prompts mention politically sensitive topics such as Tibet or Uyghurs. This behavior introduces a high-risk security threat as the AI outputs code with vulnerabilities that could be exploited if used in production environments. Although no known exploits are currently active in the wild, the potential for misuse is significant, especially in contexts where the generated code is deployed without thorough security review. European organizations using or evaluating AI-assisted coding tools, particularly those sourcing from or influenced by DeepSeek-R1, should be aware of this risk. The threat is heightened by the AI’s biased response to sensitive prompts, which may lead to inadvertent introduction of security flaws. Mitigation requires rigorous code auditing, restricting use of such AI tools for sensitive topics, and monitoring AI-generated code for security weaknesses. Countries with strong AI development sectors and geopolitical interest in China-related issues, such as Germany, France, and the UK, are more likely to be affected. Given the potential impact on confidentiality, integrity, and availability, ease of exploitation due to insecure code, and no need for user interaction beyond the prompt, the suggested severity is high.

News#infosecnews#redditGermany+5

This analysis examines the latest attack flow of the KimJongRAT variant, attributed to the North Korean threat actor Kimsuky. The malware has evolved to include both PE-based and PowerShell-based attack chains, which have been merged into a single workflow. The attackers use phishing emails for initial access, leveraging GitHub and Google Drive for malware distribution. The malware exfiltrates sensitive data including browser credentials, system information, and keystrokes. Additional activities by the same actor include credential theft through phishing sites and spear-phishing campaigns targeting South Korean users. The analysis provides evidence supporting the attribution to Kimsuky and highlights the ongoing development of variants and infrastructure, indicating successful attacks.

Malware#spear-phishing#browser credentialsGermany+5

The Shai-Hulud attack involves a widespread supply chain compromise where over 300 NPM packages and 21,000 GitHub repositories were infected within hours via a fake Bun runtime. This phishing-based attack leverages a malicious runtime impersonation to inject malicious code into popular open-source projects, potentially impacting developers and organizations relying on these packages. Although no known exploits in the wild have been reported yet, the rapid scale and targeting of widely used repositories pose a significant risk to software supply chains. The attack's medium severity reflects the potential for code integrity compromise and downstream impact on applications using these dependencies. European organizations that heavily depend on JavaScript ecosystems and open-source software development are at risk of indirect compromise. Mitigation requires proactive supply chain security measures, including dependency auditing, runtime verification, and enhanced developer awareness to detect and avoid fake runtimes. Countries with strong software development sectors and large tech industries, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. Given the attack vector and scale, the suggested severity is high due to the potential widespread impact on confidentiality, integrity, and availability of software systems without requiring user interaction but exploiting developer trust and automation.

Phishing#netsec#redditGermany+5

ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.1, 5.4.3, and 5.3.4, when the ESP32-P4 uses its hardware JPEG decoder, the software parser lacks necessary validation checks. A specially crafted (malicious) JPEG image could exploit the parsing routine and trigger an out-of-bounds array access. This issue has been fixed in versions 5.5.2, 5.4.4, and 5.3.5. At time of publication versions 5.5.2, 5.4.4, and 5.3.5 have not been released but are fixed respectively in commits 4b8f585, c79cb4d, and 34e2726.

A persistent cross-site scripting (XSS) vulnerability was discovered in esbuild, a widely used JavaScript bundler with over 5 billion downloads. This bug bypassed HTML sanitization mechanisms, allowing malicious scripts to be injected and executed in affected applications. Although no known exploits are currently in the wild, the vulnerability poses a medium risk due to its potential to compromise web application security. The flaw could lead to unauthorized data access, session hijacking, or further exploitation if leveraged by attackers. European organizations using esbuild in their web development pipelines may be at risk, especially those in sectors with heavy reliance on JavaScript frameworks. Mitigation requires updating to patched versions once available, implementing additional input validation, and employing robust Content Security Policies (CSP). Countries with significant software development industries and high adoption of modern web technologies, such as Germany, the UK, France, and the Netherlands, are more likely to be affected. Given the ease of exploitation through crafted inputs and the broad usage of esbuild, the suggested severity is medium. Defenders should prioritize monitoring for suspicious script injections and prepare to apply patches promptly.

News#netsec#redditGermany+5