970 matches found
CVE-2025-68227 mptcp: Fix proto fallback detection with BPF
In the Linux kernel, the following vulnerability has been resolved: mptcp: Fix proto fallback detection with BPF The sockmap feature allows bpf syscall from userspace, or based on bpf sockops, replacing the skprot of sockets during protocol stack processing with sockmap's custom read/write...
CVE-2025-68227
CVE-2025-68227 relates to the Linux kernel MPTCP path where sockmap/BPF can override sk_prot, causing improper protocol handling when a non-MPTCP TCP SYN is accepted. The fix makes comparison use sk_family (not sk_prot) to determine the protocol, preventing misclassification of sockets when sockm...
CVE-2025-68194 media: imon: make send_packet() more robust
In the Linux kernel, the following vulnerability has been resolved: media: imon: make sendpacket more robust syzbot is reporting that imon has three problems which result in hung tasks due to forever holding device lock 1. First problem is that when usbrxcallbackintf0 once got -EPROTO error after...
MAL-2025-192543 Malicious code in mw-proto-ts (npm)
--- -= Per source details. Do not edit below this line.=- Source: amazon-inspector d9caaea5d17e80497fb4bce0a5b6ce695c9f917c1fee32da71e8ddaa324b79c2 The package mw-proto-ts was found to contain malicious code. Source: ghsa-malware c668f66eb7f8b165c5db43b6acfc4786387faedad258459906266866c843a4ed An...
Malicious code in mw-proto-ts (npm)
--- -= Per source details. Do not edit below this line.=- Source: amazon-inspector d9caaea5d17e80497fb4bce0a5b6ce695c9f917c1fee32da71e8ddaa324b79c2 The package mw-proto-ts was found to contain malicious code. Source: ghsa-malware c668f66eb7f8b165c5db43b6acfc4786387faedad258459906266866c843a4ed An...
CVE-2025-59789 Apache bRPC: Stack Exhaustion via Unbounded Recursion in JSON Parser
Uncontrolled recursion in the json2pb component in Apache bRPC version 1.15.0 on all platforms allows remote attackers to make the server crash via sending deep recursive json data. Root Cause: The bRPC json2pb component uses rapidjson to parse json data from the network. The rapidjson parser use...
CVE-2025-59789 Apache bRPC: Stack Exhaustion via Unbounded Recursion in JSON Parser
Uncontrolled recursion in the json2pb component in Apache bRPC version 1.15.0 on all platforms allows remote attackers to make the server crash via sending deep recursive json data. Root Cause: The bRPC json2pb component uses rapidjson to parse json data from the network. The rapidjson parser use...
CVE-2025-59789
CVE-2025-59789 : Apache bRPC’s json2pb component (uses rapidjson) is vulnerable to stack/exhaustion via deeply recursive JSON input, causing server crashes. Affected: bRPC
EUVD-2025-175314
js-yaml has prototype pollution in merge...
GHSA-MH29-5H37-FV8M js-yaml has prototype pollution in merge (<<)
Impact In js-yaml 4.1.0, 4.0.0, and 3.14.1 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution proto. All users who parse untrusted yaml documents may be impacted. Patches Problem is patched in js-yaml 4.1.1 and 3.14.2...
Astro vulnerable to URL manipulation via headers, leading to middleware and CVE-2025-61925 bypass
Summary In impacted versions of Astro using on-demand rendering, request headers x-forwarded-proto and x-forwarded-port are insecurely used, without sanitization, to build the URL. This has several consequences the most important of which are: - Middleware-based protected route bypass only via...
EUVD-2025-175298
Astro vulnerable to URL manipulation via headers, leading to middleware and CVE-2025-61925 bypass...
Server-side Request Forgery (SSRF)
Overview astro is an Astro is a modern site builder with web best practices, performance, and DX front-of-mind. Affected versions of this package are vulnerable to Server-side Request Forgery SSRF via the x-forwarded-proto and x-forwarded-port headers due to improper input sanitization when...
CVE-2025-64718
CVE-2025-64718 affects js-yaml, allowing prototype pollution via proto when parsing untrusted YAML. The issue is patched in js-yaml 4.1.1 and in 3.14.2. Public IBM bulletins confirm usage of vulnerable js-yaml versions in IBM Maximo components and recommend upgrading to a fixed release (e.g., js-...
PT-2025-46851
Name of the Vulnerable Software and Affected Versions js-yaml versions prior to 4.1.1 Description js-yaml is a JavaScript YAML parser and dumper. A flaw exists where an attacker can alter the prototype of a parsed YAML document, leading to prototype pollution. This impacts users parsing untrusted...
Fedora 42 : bpfman (2025-0753bddd6c)
The remote Fedora 42 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2025-0753bddd6c advisory. This update fixes CVE-2025-0977 RUSTSEC-2025-0004, a use-after-free vulnerability in the Rust openssl crate's ssl::selectnextproto function. The openssl crat...
ROS-20251028-08
A vulnerability in the NetworkPkg/IScsiDxe/IScsiProto.c component of the EDK2 development environment for UEFI applications is associated with an with integer overflow. Exploitation of the vulnerability could allow an attacker acting remotely to compromise the integrity of the component. remotely...
SUSE CVE-2025-39990
In the Linux kernel, the following vulnerability has been resolved: bpf: Check the helper function is valid in gethelperproto kernel test robot reported verifier bug 1 where the helper func pointer could be NULL due to disabled config option. As Alexei suggested we could check on that in...
CVE-2025-39990
In the Linux kernel, the following vulnerability has been resolved: bpf: Check the helper function is valid in gethelperproto kernel test robot reported verifier bug 1 where the helper func pointer could be NULL due to disabled config option. As Alexei suggested we could check on that in...
AZL-68519 CVE-2025-39990 affecting package kernel 6.6.150.1-1
In the Linux kernel, the following vulnerability has been resolved: bpf: Check the helper function is valid in gethelperproto kernel test robot reported verifier bug 1 where the helper func pointer could be NULL due to disabled config option. As Alexei suggested we could check on that in...