Links submitted by the Threat Radar community and AI curated for defenders.

Community Curated

NCSC UK

JVN Japan

GCP Compute Engine Security

GCP Kubernetes Security

AWS Security Bulletins

CERT/CC

Tenable Research

Google Project Zero

Microsoft Security Blog

Cisco Talos

Zero Day Initiative

Palo Alto Unit 42

Krebs on Security

Kaspersky Security Blog

Check Point Research

GCVE Database

CVE Database V5

AlienVault OTX General

Real-world exploitation and exposure telemetry from the OffSeq Mirage honeypot fleet and Sonar internet scans — which CVEs attackers are actually exploiting and which are exposed in the wild, plus attacker IoCs. All IPs are masked; no raw victim or sensor identity is ever published.

OffSeq Mirage

SANS ISC Handlers Diary

SecurityWeek

Latest exploits, shellcode, and vulnerability proofs-of-concept from Exploit-DB

Exploit-DB RSS Feed

Reddit ExploitDev

Reddit ThreatIntel

Reddit BlueTeam

Reddit Reverse Engineering

Reddit Malware

Reddit Cybersecurity

Reddit NetSec

CIRCL OSINT Feed

Threatpost

ThreatFox MISP Feed

Bleeping Computer

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

org.http4s:http4s-blaze-server_2.13

org.http4s:blaze-http_2.13

org.http4s:blaze-http_3

Multiple HTTP/1.1 request-smuggling vulnerabilities exist in the blaze server's Java wire parser used by org.http4s:http4s-blaze-server_2.13. These parser laxities cause disagreement on request boundaries when paired with stricter intermediaries, potentially allowing bypass of front-end access controls, response queue poisoning, and cache poisoning. The vulnerabilities affect versions prior to 0.23.18. Exploitability depends on the presence of a fronting proxy that interprets requests differently. Deploying behind an RFC-compliant reverse proxy can mitigate the risk until an upgrade is possible.

The blaze server component of org.http4s:http4s-blaze-server_2.13 contains five independent HTTP/1.1 conformance laxities in its hand-written Java parser, leading to request-boundary disagreements with stricter intermediaries. These disagreements can be exploited when a fronting proxy forwards malformed bytes but derives different message boundaries, enabling HTTP request smuggling attacks. Such attacks can result in front-end ACL or authentication bypass, response queue poisoning on pooled backend connections, and cache poisoning. The vulnerabilities are reachable with default BlazeServerBuilder configurations and affect all versions before 0.23.18.

Detailed information about Org.http4s:http4s blaze server 2.13: blaze: Multiple HTTP/1.1 request-smuggling primitives in blaze's Java wire parser affecting null

Org.http4s:http4s blaze server 2.13: blaze: Multiple HTTP/1.1 request-smuggling primitives in blaze's Java wire parser - Live Threat Intelligence - Threat Radar | OffSeq.com

Org.http4s:http4s blaze server 2.13: blaze: Multiple HTTP/1.1 request-smuggling primitives in blaze's Java wire parser

Threats Tagged 'ghsa-mhvj-jhpq-885v'