# remote code execution Published articles for remote code execution. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## \[webapps\] Metabase 0.61.0 - Authenticated Remote Code Execution DevFeed: [\[webapps\] Metabase 0.61.0 - Authenticated Remote Code Execution]() Original publisher: [Read original article]() Author: Gutierre0x80 Published: 2026-09-03T00:00:00Z Content type: article Language: en Sources: [Exploit-DB.com RSS Feed]() Topics: [Exploit](), [webapps]() Tags: [2026](), [cve](), [cve-2026-59827](), [execution](), [exploit](), [multiple](), [remote](), [remote-code-execution](), [webapps]() ### AI overview An Exploit-DB entry identifies authenticated remote code execution affecting Metabase 0.61.0 and associates it with CVE-2026-59827. ### Source excerpt Metabase 0.61.0 - Authenticated Remote Code Execution ## \[webapps\] FreePBX 17.0.2 - Remote Code Execution (RCE) DevFeed: [\[webapps\] FreePBX 17.0.2 - Remote Code Execution (RCE)]() Original publisher: [Read original article]() Author: Jared Brits Published: 2026-09-03T00:00:00Z Content type: article Language: en Sources: [Exploit-DB.com RSS Feed]() Topics: [Exploit](), [webapps](), [Code]() Tags: [cve](), [cve-2025-57819](), [exploit](), [multiple](), [platform](), [remote-code-execution](), [webapps]() ### AI overview An exploit entry describing remote code execution affecting FreePBX 17.0.2, associated with CVE-2025-57819. ### Source excerpt FreePBX 17.0.2 - Remote Code Execution (RCE) ## \[webapps\] Ghost\_CMS 6.19.0 - Remote Code Execution DevFeed: [\[webapps\] Ghost\_CMS 6.19.0 - Remote Code Execution]() Original publisher: [Read original article]() Author: Maksim Rogov Published: 2026-09-02T00:00:00Z Content type: article Language: en Sources: [Exploit-DB.com RSS Feed]() Topics: [Exploit](), [webapps]() Tags: [cve](), [cve-2026-29053](), [exploit](), [multiple](), [remote-code-execution](), [webapps]() ### AI overview An Exploit Database entry identifies a remote code execution exploit affecting Ghost_CMS 6.19.0, associated with CVE-2026-29053 and listed for multiple platforms. ### Source excerpt Ghost_CMS 6.19.0 - Remote Code Execution ## \[webapps\] Langflow 1.8.4 - Path Traversal to Remote Code Execution DevFeed: [\[webapps\] Langflow 1.8.4 - Path Traversal to Remote Code Execution]() Original publisher: [Read original article]() Author: cardosource Published: 2026-08-31T00:00:00Z Content type: article Language: en Sources: [Exploit-DB.com RSS Feed]() Topics: [Exploit]() Tags: [cve](), [cve-2026-5027](), [exploit](), [multiple](), [remote-code-execution](), [webapps]() ### AI overview An exploit record identifies a path traversal vulnerability in Langflow 1.8.4 that can lead to remote code execution. It references CVE-2026-5027. ### Source excerpt Langflow 1.8.4 - Path Traversal to Remote Code Execution ## Vercel applications are protected from Next.js August 2026 security vulnerabilities DevFeed: [Vercel applications are protected from Next.js August 2026 security vulnerabilities]() Original publisher: [Read original article]() Author: Karim Rahal Published: 2026-08-25T16:39:17Z Content type: article Language: en Sources: [Vercel News]() Topics: [Next.js](), [Vulnerabilities](), [Security](), [Vercel](), [AVIF Images](), [Cache](), [Linux]() Tags: [avif-images](), [cve](), [dependency](), [linux](), [next-js](), [remote-code-execution](), [security](), [upgrade](), [vercel](), [vulnerabilities]() ### AI overview Vercel reports two critical Next.js vulnerabilities disclosed in the August 2026 Security Release. Vercel-hosted applications are protected without customer action, while self-hosted applications should upgrade to patched versions. ### Source excerpt Summary Two vulnerabilities affecting Next.js were disclosed in the August 2026 Security Release. Next.js applications hosted on Vercel are protected and require no customer action. Next.js August 2026 vulnerabilities Next.js disclosed the following critical vulnerabilities: GHSA-2xp9-vwfh-vxw4 originates in the upstream libheif dependency and can lead to unauthenticated remote code execution when Image Optimization processes a crafted AVIF input. CVE-2026-75604 (GHSA-p293-qw3h-jr36) can lead to unauthenticated remote code execution on Windows-hosted Next.js servers in applications using the Pages Router and App Router without Cache Components. After the AVIF vulnerability was identified, Vercel applied protections to its managed Image Optimization service. Impact on Vercel deployments Applications hosted on Vercel are protected. No upgrades, configuration changes, or redeploys are required. Once the AVIF vulnerability was identified, Vercel disabled AVIF optimization across its managed Image Optimization service. AVIF inputs are served as-is and do not pass through the affected processing path. The second vulnerability only affects servers using a Windows filesystem. Vercel's Next.js runtime uses Linux and is not affected. Resolution for self-hosted applications Self-hosted Next.js applications should upgrade to the appropriate patched version. For applications running Next.js 15.x or earlier: For applications running Next.js 16.x: In the patched releases, AVIF images are not resized or optimized. They are served as-is until a fixed libheif version is available. There is no workaround for the Windows vulnerability; affected servers should upgrade immediately. Credit Thanks to the Hacktron team for responsibly disclosing the AVIF vulnerability, and to evolutionstorm and B0RI for responsibly disclosing the Windows vulnerability. References Next.js August 2026 security release GHSA-2xp9-vwfh-vxw4 Upstream libheif advisory GHSA-p293-qw3h-jr36 Read more ## \[webapps\] Joomla JCE\_2.9.15 - Remote Code Execution DevFeed: [\[webapps\] Joomla JCE\_2.9.15 - Remote Code Execution]() Original publisher: [Read original article]() Author: Jared Brits Published: 2026-08-17T00:00:00Z Content type: article Language: en Sources: [Exploit-DB.com RSS Feed]() Topics: [Exploit](), [webapps]() Tags: [cve](), [cve-2026-48907](), [exploit](), [multiple](), [remote-code-execution](), [webapps]() ### AI overview A record describing a remote code execution exploit affecting Joomla JCE 2.9.15, identified as CVE-2026-48907 and categorized under web applications for multiple platforms. ### Source excerpt Joomla JCE_2.9.15 - Remote Code Execution ## \[remote\] PraisonAI praisonaiagents 1.6.77 - Remote Code Execution DevFeed: [\[remote\] PraisonAI praisonaiagents 1.6.77 - Remote Code Execution]() Original publisher: [Read original article]() Author: banyamer Published: 2026-08-11T00:00:00Z Content type: article Language: en Sources: [Exploit-DB.com RSS Feed]() Topics: [Exploit]() Tags: [cve](), [cve-2026-61447](), [exploit](), [multiple](), [remote](), [remote-code-execution]() ### AI overview This entry reports a remote code execution exploit affecting PraisonAI praisonaiagents version 1.6.77, identified as CVE-2026-61447. ### Source excerpt PraisonAI praisonaiagents 1.6.77 - Remote Code Execution ## Nuxt July 2026 security advisory DevFeed: [Nuxt July 2026 security advisory]() Original publisher: [Read original article]() Author: Sage Abraham Published: 2026-07-27T00:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Nuxt.js](), [Security](), [Vulnerabilities](), [Authorization](), [Caching](), [Vercel]() Tags: [authorization](), [cache](), [caching](), [cve](), [development](), [nuxt](), [remote-code-execution](), [security](), [upgrade](), [vercel](), [vulnerabilities]() ### AI overview The Nuxt team released Nuxt 4.5.1, Nuxt 3.21.10, and @nuxt/devtools 3.3.1 to fix eight security advisories, including a high-severity server-side remote code execution vulnerability. Vercel deployed WAF mitigations for direct exploitation of that vulnerability, but users must still upgrade because other issues affect component instantiation, caching, authorization, denial of service, and development tooling. ### Source excerpt The Nuxt team has released Nuxt 4.5.1 and 3.21.10, along with @nuxt/devtools 3.3.1, to address eight security advisories, including a high-severity server-side remote code execution vulnerability. Vulnerabilities addressed Vulnerability Severity Advisory Server-side remote code execution via server island props High GHSA-9473-5f9j-94wq Unauthorized component instantiation via server island props Medium GHSA-48hr-524c-v5w3 Route rule authorization bypass High GHSA-hxvh-4h3w-prp9 Server component denial of service High GHSA-hxcr-hm88-mpq6, GHSA-9pgf-384g-p7mv Cross-user disclosure of cached payloads, affecting Nuxt 4.x versions 4.4.0 and later High GHSA-wm8w-6qjm-cv43 Development server path disclosure Low GHSA-7c4v-fwgw-9rf7 Remote code execution in Nuxt DevTools, development-only, fixed in @nuxt/devtools 3.3.1 Critical GHSA-279x-mwfv-vcqv Vercel platform protections Vercel received advance notice of the server-side remote code execution vulnerability, GHSA-9473-5f9j-94wq, and deployed platform-wide WAF mitigations before public disclosure. Applications deployed on Vercel are automatically protected by these mitigations, with no configuration changes required. However, do not rely on them for full protection. Upgrading to a patched version is still required. The WAF mitigations cover only direct exploitation of the server-side RCE. The remaining component-instantiation, caching, authorization, denial-of-service, and development-time vulnerabilities require upgrading Nuxt and Nuxt DevTools. Recommended action All Nuxt users should upgrade as soon as possible: Nuxt 4: 4.5.1 or later Nuxt 3: 3.21.10 or later Nuxt DevTools: 3.3.1 or later To upgrade, run: This also refreshes the lockfile, pulling in the patched Nuxt DevTools version. Users who previously upgraded for the earlier route rule advisory, CVE-2026-53721, must still upgrade. The newly disclosed authorization bypass is a regression in that earlier fix. Nuxt 4 users who cache authenticated pages containing user-s ## Mitigating WordPress attacks with containers DevFeed: [Mitigating WordPress attacks with containers]() Original publisher: [Read original article]() Published: 2026-07-27T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [WordPress](), [Containers](), [Exploit](), [Vulnerabilities]() Tags: [chainguard-containers](), [containers](), [database](), [distroless](), [files](), [hardened-containers](), [remote-code-execution](), [software-supply-chain-security](), [vulnerabilities](), [wordpress](), [wordpress-cves]() ### AI overview This article examines the wp2shell attack, in which two WordPress vulnerabilities can be chained to achieve remote code execution. It explains that hardened, distroless containers and read-only filesystems can limit an attacker's capabilities and simplify recovery, while emphasizing the need to update WordPress immediately. ### Source excerpt The wp2shell WordPress exploit enables remote code execution. Learn how hardened containers help reduce the blast radius of compromise. ## Bringing Rust to the Pixel Baseband DevFeed: [Bringing Rust to the Pixel Baseband]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2026-04-10T15:12:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [Rust](), [Memory Safety](), [Security](), [Parsing](), [Google]() Tags: [android](), [android-security](), [dns](), [google](), [internet](), [library](), [memory-safety](), [none](), [open-source](), [parsing](), [pixel](), [remote-code-execution](), [rust](), [security](), [test-coverage](), [vulnerabilities]() ### AI overview Google describes integrating a memory-safe Rust DNS parser into Pixel modem firmware. The post explains the security motivation, the modem's remote attack surface, and the evaluation of open-source Rust DNS libraries, identifying hickory-proto as the best candidate based on maintenance, test coverage, and adoption. ### Source excerpt Posted by Jiacheng Lu, Software Engineer, Google Pixel Team Google is continuously advancing the security of Pixel devices. We have been focusing on hardening the cellular baseband modem against exploitation. Recognizing the risks associated within the complex modem firmware, Pixel 9 shipped with mitigations against a range of memory-safety vulnerabilities. For Pixel 10, Google is advancing its proactive security measures further. Following our previous discussion on "Deploying Rust in Existing Firmware Codebases", this post shares a concrete application: integrating a memory-safe Rust DNS(Domain Name System) parser into the modem firmware. The new Rust-based DNS parser significantly reduces our security risk by mitigating an entire class of vulnerabilities in a risky area, while also laying the foundation for broader adoption of memory-safe code in other areas. Here we share our experience of working on it, and hope it can inspire the use of more memory safe languages in low-level environments. Why Modem Memory Safety Can't Wait In recent years, we have seen increasing interest in the cellular modem from attackers and security researchers. For example, Google's Project Zero gained remote code execution on Pixel modems over the Internet. Pixel modem has tens of Megabytes of executable code. Given the complexity and remote attack surface of the modem, other critical memory safety vulnerabilities may remain in the predominantly memory-unsafe firmware code. Why DNS? The DNS protocol is most commonly known in the context of browsers finding websites. With the evolution of cellular technology, modern cellular communications have migrated to digital data networks; consequently, even basic operations such as call forwarding rely on DNS services. DNS is a complex protocol and requires parsing of untrusted data, which can lead to vulnerabilities, particularly when implemented in a memory-unsafe language (example: CVE-2024-27227). Implementing the DNS parser in Rust offers va ## exploits.club Weekly(ish) Newsletter 94 - P20 VMWare Bugs, ExpDev With LLMs, Pixel 0-Click Bugs, and More DevFeed: [exploits.club Weekly(ish) Newsletter 94 - P20 VMWare Bugs, ExpDev With LLMs, Pixel 0-Click Bugs, and More]() Original publisher: [Read original article]() Author: exploits.club Published: 2026-01-30T16:00:22Z Content type: article Language: en Sources: [exploits.club]() Topics: [Security](), [Exploit](), [Large Language Model](), [Artificial Intelligence](), [Code](), [Claude](), [ChatGPT](), [Network architectures](), [P2P](), [Open Source](), [Linux]() Tags: [ai](), [chatgpt](), [code](), [exploit](), [linux](), [llms](), [network](), [open-source](), [peer](), [poc](), [rce](), [remote-code-execution](), [security]() ### AI overview This newsletter surveys recent security research, including experiments using Claude and ChatGPT to generate proofs of concept for QuickJS vulnerabilities, a wormable remote code execution chain in Command & Conquer, a MediaTek bootloader exploit, and VMware workstation research. ### Source excerpt Good morning friends....been a minute. But we are SO back. Annnnnyways 👇 In Case You Missed It... RE//verse Tickets Still On Sale - If you were just at DistrictCon, escape the snow-pocalypse to Florida next month OffensiveCon CFP - 30 days to get-em submitted! Resources And Write-Ups ## Revisiting CVE-2025-50165: A critical flaw in Windows Imaging Component DevFeed: [Revisiting CVE-2025-50165: A critical flaw in Windows Imaging Component]() Original publisher: [Read original article]() Author: Romain Dumont Published: 2025-12-22T09:55:00Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [Vulnerabilities](), [Windows](), [Exploit](), [Code](), [Library]() Tags: [analysis](), [cve](), [deep-dive](), [encoding](), [eset-research](), [jpeg](), [library](), [remote-code-execution](), [root-cause-analysis](), [vulnerability](), [windows]() ### AI overview ESET analyzes CVE-2025-50165, a critical Windows Imaging Component vulnerability in WindowsCodecs.dll. The flaw involves an uninitialized function-pointer dereference during JPG compression and re-encoding, and the article reassesses how difficult the vulnerability is to exploit. ### Source excerpt A comprehensive analysis and assessment of a critical severity vulnerability with low likelihood of mass exploitation ## Security Advisory: CVE-2025-66478 DevFeed: [Security Advisory: CVE-2025-66478]() Original publisher: [Read original article]() Author: Sebastian Markbåge Published: 2025-12-03T16:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [vulnerability](), [Exploit](), [React](), [Protocol (disambiguation)]() Tags: [cve](), [next-js](), [protocol](), [react](), [remote-code-execution](), [security](), [upgrade](), [vulnerability]() ### AI overview This security advisory describes CVE-2025-66478, a critical vulnerability in the React Server Components protocol that affects certain Next.js applications using the App Router. Under specific conditions, attacker-controlled requests could lead to remote code execution. Users are advised to upgrade to patched Next.js releases immediately. ### Source excerpt A critical vulnerability (CVE-2025-66478) has been identified in the React Server Components protocol. Users should upgrade to patched versions immediately. ## Security Advisory: Critical RCE Vulnerabilities in React Server Components (CVE-2025-55182) DevFeed: [Security Advisory: Critical RCE Vulnerabilities in React Server Components (CVE-2025-55182)]() Original publisher: [Read original article]() Author: Stephen Thoemmes Published: 2025-12-03T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [React](), [Vulnerabilities](), [Next.js](), [Exploit](), [Security](), [Flight](), [HTTP]() Tags: [awareness](), [blog](), [cloud-security](), [code-security](), [container-security](), [cve](), [developer](), [devrel](), [docker](), [engineering](), [http](), [incident](), [next-js](), [react](), [remote](), [remote-code-execution](), [security](), [upgrade](), [vulnerabilities](), [vulnerability-insights]() ### AI overview The article reports critical unauthenticated remote code execution vulnerabilities in React Server Components and Next.js caused by unsafe deserialization of attacker-controlled data in the RSC "Flight" protocol. It explains that default configurations were exploitable, identifies affected React and Next.js releases and other tools embedding RSC, and urges immediate patching. ### Source excerpt Critical RCE vulnerabilities (CVE-2025-55182/CVE-2025-66478) were found in React Server Components and Next.js via unsafe deserialization. Immediate upgrade to patched versions is mandatory to prevent unauthenticated remote code execution. Learn how to detect and mitigate the critical flaw. ## Microauthorization: Why Microservices can be Great for Security Hygiene DevFeed: [Microauthorization: Why Microservices can be Great for Security Hygiene]() Original publisher: [Read original article]() Published: 2025-05-08T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Architecture & Design](), [microservices architecture](), [Security](), [Authorization](), [IAM]() Tags: [architecture](), [authorization](), [container-security](), [iam](), [least-privilege](), [microauthorization](), [microservices](), [remote-code-execution](), [security]() ### AI overview The article argues that decomposing monolithic applications into microservices can improve security hygiene by isolating processes and assigning each service a distinct identity with narrower IAM capabilities. It explains that service-to-service authorization can limit the blast radius of a breach, although attackers may still need to move laterally across services. ### Source excerpt Microservices can enable you to easily independently roll out services, but they can also provide security benefits. Learn more with Chainguard CTO Matt Moore. ## Ingress-nginx-controller: Nightmare on CVE Street DevFeed: [Ingress-nginx-controller: Nightmare on CVE Street]() Original publisher: [Read original article]() Published: 2025-04-02T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [nginx](), [Vulnerabilities](), [Security](), [Kubernetes](), [chainguard containers](), [chainguard os](), [chainguard]() Tags: [availability](), [chainguard](), [chainguard-containers](), [chainguard-os](), [container-images](), [containers](), [cve](), [cves](), [ingress](), [ingress-nginx](), [kubernetes](), [nginx](), [remote-code-execution](), [security](), [vulnerabilities](), [wiz]() ### AI overview The article describes several critical remote code execution vulnerabilities affecting the Ingress-nginx-controller, including risks to Kubernetes cluster secrets, service availability, privileges, and security controls. It also explains how Chainguard reviewed its infrastructure, identified affected Chainguard Containers, and prepared patches using Chainguard OS's continuous update model. ### Source excerpt Chainguard was able to quickly respond to and handle the recent ingress-nginx-controller CVEs that were discovered by Wiz. See the actions we have taken. ## Zero-day RCE vulnerability found in CUPS - Common UNIX Printing System DevFeed: [Zero-day RCE vulnerability found in CUPS - Common UNIX Printing System]() Original publisher: [Read original article]() Author: Jim Armstrong Published: 2024-09-27T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Unix](), [Vulnerabilities](), [Security](), [Exploit](), [Linux](), [Containers](), [C](), [C++]() Tags: [attacks](), [awareness](), [blog](), [c](), [c-plus-plus](), [container-security](), [containers](), [cve](), [cves](), [dns](), [docker](), [engineering](), [executive](), [interest](), [linux](), [network](), [open-source-security](), [pmm](), [port](), [rce](), [remote-code-execution](), [scm](), [security](), [snyk](), [snyk-apprisk](), [snyk-container](), [snyk-open-source](), [vulnerabilities](), [vulnerability]() ### AI overview The article reports several vulnerabilities in CUPS, the Common UNIX Printing System, including unauthenticated remote code execution. It discusses four associated CVEs, a potentially high CVSS score, affected UNIX and Linux packages, exploitability conditions involving UDP port 631 or DNS-SD, and remediation assessment using Snyk Open Source and Snyk Container. ### Source excerpt Security researcher evilsocket.net (Simone Margaritelli) published information about several vulnerabilities in CUPS that allow for remote code execution (RCE) ## Understanding attacker techniques in distroless containers DevFeed: [Understanding attacker techniques in distroless containers]() Original publisher: [Read original article]() Published: 2023-10-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [distroless](), [Containers](), [Security](), [container-security](), [Vulnerabilities]() Tags: [chainguard](), [chainguard-images](), [container-security](), [containers](), [distroless](), [distroless-containers](), [exploit](), [rce](), [remote-code-execution](), [security](), [vulnerabilities]() ### AI overview The article examines attacker techniques relevant to distroless containers, drawing on a DEFCON 31 talk and an example involving PHP remote code execution, reverse shells, and injected spam content. It emphasizes keeping software up to date and using defense in depth. ### Source excerpt Explore DEFCON 31 insights on Distroless container security. Delve into RCE vulnerabilities and Chainguard's robust defense strategies for up-to-date software. ## Swift deserialization security primer DevFeed: [Swift deserialization security primer]() Original publisher: [Read original article]() Author: Sam Sanoop Published: 2023-07-18T16:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Swift](), [Security](), [Vulnerabilities](), [Code](), [Protocol (disambiguation)]() Tags: [apis](), [attacks](), [awareness](), [blog](), [code](), [code-security](), [developer](), [distributed](), [engineering](), [exploit](), [remote-code-execution](), [security](), [security-vulnerabilities](), [serialization](), [swift](), [vulnerabilities]() ### AI overview This Swift security primer explains how deserialization vulnerabilities can arise when using NSCoding and NSSecureCoding. It describes object substitution attacks, potential remote code execution, command injection, and stricter protections provided by NSSecureCoding. ### Source excerpt This blog will detail deserialization vulnerabilities in Swift that can occur when using the popular APIs, NScoding and NSSecureCoding, and how to prevent it properly. ## Making Open Source Safer for Everyone with Shopify's Bug Bounty Program DevFeed: [Making Open Source Safer for Everyone with Shopify's Bug Bounty Program]() Original publisher: [Read original article]() Author: Zack Deveau Published: 2022-06-15T18:00:02Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Application Security](), [Rails](), [vulnerability](), [Bug Bounty](), [Security](), [Open Source](), [Ruby]() Tags: [application-security](), [bug-bounty](), [open-source](), [rails](), [remote-code-execution](), [ruby](), [serialization](), [shopify](), [vulnerability]() ### AI overview Shopify describes how a bug bounty report led to contributions that improve the security of the Rails library. The report identified a deserialization vulnerability in ActiveSupport's MessageEncryptor, where leaked development secrets could enable seemingly trusted data and potentially remote code execution. Shopify addressed the issue in its system, helped Rails adopt safer default serializers, and developed tools to help Ruby application developers identify similar risks. ### Source excerpt Zack Deveau, Senior Application Security Engineer at Shopify, shares the details behind a recent contribution to the Rails library, inspired by a bug bounty report we received. He'll go over the report and its root cause, how we fixed it in our system, and how we took it a step further to make Rails more secure by updating the default serializer for a few classes to use safe defaults. ## Log4j Vulnerability Update DevFeed: [Log4j Vulnerability Update]() Original publisher: [Read original article]() Author: James Brooks Published: 2021-12-15T13:14:00Z Content type: news Language: en Sources: [Laravel Blog]() Topics: [vulnerability](), [Java](), [Library](), [Exploit](), [elasticsearch](), [Laravel]() Tags: [apache](), [docker](), [elasticsearch](), [java](), [laravel](), [library](), [log4j](), [news](), [remote-code-execution](), [script](), [vulnerability]() ### AI overview This update explains the Log4Shell vulnerability in Apache Log4j, a Java logging library that can allow remote code execution through a specific string. Laravel Forge and Laravel Vapor do not install or use Log4j by default, but manually installed applications, libraries, custom layers, or customized environments may still be affected and should be checked. ### Source excerpt Log4j is a Java library by Apache used to log debug messages within applications. It's recently been featured in news outlets around the world due to a vulnerability (known as Log4Shell) that was discovered allowing remote code execution using a specific string. ## Dealing with the Critical Log4j Vulnerability DevFeed: [Dealing with the Critical Log4j Vulnerability]() Original publisher: [Read original article]() Author: Kyle Moore Published: 2021-12-13T05:00:00Z Content type: tutorial Language: en Sources: [The Gradle Blog]() Topics: [log4j](), [vulnerability](), [CVE-2021-44228](), [Gradle](), [Logging]() Tags: [apache](), [cve-2021-44228](), [gradle](), [log4j](), [logging](), [remote-code-execution](), [upgrade](), [vulnerabilities](), [vulnerability]() ### AI overview This advisory explains the critical remote code execution vulnerability in Apache Log4j, identifies affected versions, and provides Gradle users with steps to detect vulnerable dependencies, upgrade Log4j, and protect project and build dependencies. It also clarifies that the Gradle Build Tool itself does not use Log4j. ### Source excerpt A critical remote code execution (RCE) vulnerability has been identified in the popular Apache Log4j logging library that affects versions 2.0 up to and including 2.14.1. This vulnerability has affected a very large number of JVM-based systems. For more information on the vulnerability itself, see CVE-2021-44228. Update (December 22, 2021): Since the first post, two other vulnerabilities have been identified - CVE-2021-45046 and CVE-2021-45105 - so make sure to go over the different sections for updated instructions. This vulnerability is being actively exploited. All Gradle users should assess whether their software projects are vulnerable and, if necessary, update to Log4j 2.17.0 or newer as soon as possible. We have provided instructions below on how to identify and prevent this vulnerability in your project. We strongly recommended that you configure your Gradle build to reject any vulnerable version of Log4j using a dependency constraint. In addition to your project dependencies, we also recommend protecting your build dependencies as documented below. Note that the Gradle Build Tool itself is not impacted by this vulnerability as it does not use Log4j. Gradle uses SLF4J and a custom logging implementation not susceptible to the vulnerable string substitution. The Gradle Scala plugin uses the Zinc Scala compiler that has a dependency on a vulnerable version of Log4j. However, in this case Gradle also supplies its own logging implementation and Log4j is not used by default. Updates to this post: Updated on December 14th Updated on December 15th Updated on December 22nd Updated on December 30th Protecting your project dependencies 1. Identify if your project uses a vulnerable Log4j version First, verify if your project uses the vulnerable Log4j version using the dependencies report or a Build Scan™. See viewing and debugging dependencies for details. All versions of org.apache.logging.log4j:log4j-core between 2.0 and 2.16.0 (inclusive) are vulnerable. 2. Upgrade ## How a malicious pull request could expose cloud infrastructure credentials DevFeed: [How a malicious pull request could expose cloud infrastructure credentials]() Original publisher: [Read original article]() Author: info@goteleport.com (Walt Della) Published: 2021-09-16T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [vulnerability](), [Pull Request](), [Kubernetes](), [Amazon Web Services](), [CI/CD](), [Docker](), [GitHub]() Tags: [aws](), [ci-cd](), [docker](), [github](), [kubernetes](), [pull-request](), [remote-code-execution](), [vulnerability]() ### AI overview This blog post analyzes a vulnerability in Teleport's former CI environment in which code from an unapproved external pull request could escape isolation, pivot through Kubernetes workloads to CI infrastructure, and expose production AWS credentials. The article says the CI system was fixed and that the response team found no evidence of exploitation or data tampering. ### Source excerpt In this blog post we'll explain how an attacker can get access into a cloud environment by sending a malicious pull request. ## Proxies are complicated: RCE vulnerability in a 3 million downloads/week NPM package DevFeed: [Proxies are complicated: RCE vulnerability in a 3 million downloads/week NPM package]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2021-08-31T11:00:00Z Content type: article Language: en Sources: [HTTP Toolkit]() Topics: [vulnerability](), [npm](), [Node.js](), [HTTP](), [Network](), [Amazon Web Services](), [Firebase]() Tags: [aws](), [cli](), [command-line](), [dependencies](), [dependency](), [env-file-security](), [firebase](), [firebase-cli](), [github](), [http](), [javascript](), [network](), [node-js](), [npm](), [remote-code-execution](), [remote-code-execution-vulnerability](), [security](), [vulnerability]() ### AI overview The article examines CVE-2021-23406, a high-severity remote code execution vulnerability in the Pac-Resolver NPM dependency. The issue can affect Node.js applications using untrusted PAC or proxy configuration, and was fixed in Pac-Resolver v5.0.0 and related packages. ### Source excerpt Pac-Resolver, a widely used NPM dependency, had a high-severity RCE (Remote Code Execution) vulnerability that could allow network administrators or other malicious actors on your local network to remotely run arbitrary code inside your Node.js process whenever you tried to send an HTTP request. This is bad! This package is used for PAC file support in Pac-Proxy-Agent, which is used in turn in Proxy-Agent, which then used all over the place as the standard go-to package for HTTP proxy autodetection & configuration in Node.js. It's very popular: Proxy-Agent is used everywhere from AWS's CDK toolkit to the Mailgun SDK to the Firebase CLI (3 million downloads per week in total, and 285k public dependent repos on GitHub). I found this lovely little issue a short while back, while adding proxy support to HTTP Toolkit (yes, code reviewing your dependencies is a good idea!). The vulnerability was fixed in v5.0.0 of all those packages recently, and was formally disclosed last week as CVE-2021-23406. First things first: are you personally at risk? This vulnerability seriously affects you if: You depend on Pac-Resolver before v5.0.0 (even transitively) in a Node.js application And, you do one of the below: Explicitly use PAC files for proxy configuration. Read & use the operating system proxy configuration in Node.js, on systems with WPAD enabled. Use proxy configuration (env vars, config files, remote config endpoints, command-line arguments) from any other source that you wouldn't 100% trust to freely run code on your computer. In any of those cases, an attacker (by configuring a malicious PAC URL, intercepting PAC file requests with a malicious file, or using WPAD) can remotely run arbitrary code on your computer any time you send an HTTP request using this proxy configuration. If you're in this situation, you need to update (to Pac-Resolver v5 and/or Proxy-Agent v5) right now. If not, you're probably not in any immediate risk (but it's a good idea to update anyway). For n [Next page]()