CVE-2024-24919-Bulk-Scanner

CVE-2024-24919 대량 스캐너 CVE-2024-24919 Check Point Security Gateway 정보 노출 이 스크립트는 다음에 기반하며, 크레딧은 다음으로 갑니다: https://labs.watchtowr.com/check-point-wrong-check-point-cve-2024-24919/ 이 Python 스크립트는 URL 목록을 스캔하여 CVE-2024-24919 취약점을 찾기 위해 특정 POST 요청을 보내고 응답 헤더와 상태 코드를 확인합니다. 요청 및 응답 세부 정보를 기록하고 사전 정의된 기...

CVE-2023-35813

CVE-2023-35813 CVE-2023-35813은 서버 응답 헤더 변조를 분석하여 Sitecore 인스턴스가 취약한지 확인하는 데 사용되는 개념 증명PoC입니다. heretic이 3를 담아 만들었습니다...

CVE-2017-1000486

CVE-2017-1000486 PrimeFaces 5.x용 원격 코드 실행 익스플로잇 - EL 인젝션 CVE-2017-1000486 이는 기본적으로 Mogwailabs가 만든 동일한 익스플로잇이지만, 인터넷에 접근할 수 없거나 방화벽 아웃바운드 트래픽이 차단된 폐쇄 환경에서 작동하도록 수정되었습니다. HTTP 응답 헤더에 결과를 제공하므로, 이전 익스플로잇으로 블라인드 RCE를 시도하는 경우 더 이상 필요하지 않습니다. 사용법 python3 primefaces.py -t vulnapp.com id 정확한 엔드포인트를 위해...

CVE-2026-Mastodon-Streaming-CRLF-Injection

CVE-2026-XXXXX: Mastodon Streaming Server의 HTTP 응답 헤더 인젝션 CRLF 취약점 개요 항목| 내용 ---|--- CVE ID| CVE-2026-XXXXX 영향을 받는 제품| Mastodon Streaming Server 영향을 받는 버전| $key: $headerskey.join' ' ; 영향 HTTP 헤더 인젝션: 임의의 HTTP 헤더 주입 HTTP 응답 분할: 두 번째 HTTP 응답 본문 주입 캐시 포이즈닝 정보 노출: 내부 오류 메시지가 인증되지 않은 사용자에게 노출됨 개념 증명...

CVE-2026-66746-HTTP-Response-Splitting-via-Unvalidated-Response-Header-Values-rouille-

보안 권고: 검증되지 않은 응답 헤더 값으로 인한 HTTP 응답 분할 rouille 지정 CVE ID: CVE-2026-66746 요약 rouille는 응답 헤더 값을 캐리지 리턴 또는 라인 피드 검사 없이 클라이언트에 기록합니다. 따라서 공격자의 영향을 받은 텍스트를 헤더 값에 넣는 애플리케이션은 추가 헤더 또는 두 번째 HTTP 응답 전체를 네트워크로 내보내게 됩니다. rouille의 두 가지 속성으로 인해 일반적인 코드에서도 이 취약점에 도달할 수 있습니다. Request::getparam은 퍼센트 디코딩을 수행하므로 쿼...

CVE-2026-27944

CVE-2026-27944 - Nginx UI 무인증 백업 다운로드 및 복호화 https://img.shields.io/badge/python-3.6+-blue.svg https://img.shields.io/badge/license-MIT-green https://img.shields.io/badge/PoC-Exploit-red CVE‑2026‑27944에 대한 PoCproof‑of‑concept 익스플로잇입니다. 이는 Nginx UI ≤ 2.3.2의 치명적인 취약점으로, 인증되지 않은 공격자가 /api/backup 엔드포인...

UBUNTU-CVE-2026-93711

Dancer2 versions before 2.2.0 for Perl do not strip CR and LF from response header names in headerstoarray. The routine removes CR and LF from each header value but not from the name. A name carrying them therefore reaches the PSGI server intact. A server that does not validate keys writes it to...

CVE-2026-93711

Dancer2 versions before 2.2.0 for Perl do not strip CR and LF from response header names in headerstoarray. The routine removes CR and LF from each header value but not from the name. A name carrying them therefore reaches the PSGI server intact. A server that does not validate keys writes it to...

SUSE CVE-2026-85732

oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, the parseLink function in registry/remote/utils.go accepts an absolute URL from a registry-controlled Link response header without validating its scheme, host, or port. Tags, Referrers, and Repositories pagination operations then...

CVE-2026-85077 Sanic: HTTP response header injection via missing CR/LF validation in Sanic HTTP/1.1 responses

Sanic is an opensource python web server/framework. Prior to version 24.12.1, and in version 25.12.0, the HTTP/1.1 response pipeline in sanic/response/types.py serializes response header names and values without rejecting carriage-return or line-feed characters. Applications that place...

PT-2026-93849

Name of the Vulnerable Software and Affected Versions oras-go versions prior to 2.6.2 Description The parseLink function in registry/remote/utils.go fails to validate the scheme, host, or port of absolute URLs provided in the Link response header from a registry. This allows a malicious registry ...

Astra Linux – Vulnerability in Apache2

Before Apache HTTP Server 2.4.55, a malicious backend could cause the response headers to be truncated early, resulting in some headers being incorporated into the response body. If the later headers serve any security purposes, they will not be interpreted by the client...

Astra Linux - Vulnerability in Squid

A vulnerability was discovered in Squid 4.x versions prior to 4.15 and 5.x versions prior to 5.0.6. If a remote server sends a specific response header via HTTP or HTTPS, it results in a denial of service. This header could plausibly occur in normal network traffic...

httpd: incomplete fix for CVE-2023-38709

A flaw was found in httpd. The response headers are not sanitized before an HTTP response is sent when a malicious backend can insert a Content-Type, Content-Encoding, or some other headers. These issues lead to HTTP response splitting. This CVE provides a "complete" fix for CVE-2023-38709...

CVE-2026-84933

undici's cache interceptor does not handle the Set-Cookie response header anywhere in its cache path, so it neither refuses to store nor strips that header. In shared cache mode, which is the default, an otherwise cacheable response that carries a Set-Cookie header, for example one marked with a...

httpc memory exhaustion via unbounded response header accumulation

...

Security Bulletin: XSS Security Vulnerability in response header affects IBM Sterling B2B Integrator and IBM Sterling File Gateway (CVE-2025-36431)

Summary IBM Sterling B2B Integrator and IBM Sterling File Gateway have addressed XSS vulnerability. Vulnerability Details CVEID:CVE-2025-36431 DESCRIPTION: IBM Sterling B2B Integrator 6.2.2.0 through 6.2.2.01 and IBM Sterling File Gateway 6.2.2.0 through 6.2.2.01 is vulnerable to cross-site...

CVE-2026-48769

A flaw was found in Incus, a container and virtual machine manager. A malicious image server can cause the Incus client to write files to arbitrary locations via a crafted response header, potentially leading to command execution as root. Mitigation No mitigation is needed as Incus is not shipped...

CVE-2026-71572

Joomla! Core - 20260801 - Response header injection in download views in Joomla 3.0.0-5.4.7, 6.0.0-6.1.2 - Lack of output processing allowed a header injection in the multiple download views, leading to reflected file download / content-type confusion...

CVE-2026-71572 Joomla! Core - [20260801] - Response header injection in download views in Joomla 3.0.0-5.4.7, 6.0.0-6.1.2

Joomla! Core - 20260801 - Response header injection in download views in Joomla 3.0.0-5.4.7, 6.0.0-6.1.2 - Lack of output processing allowed a header injection in the multiple download views, leading to reflected file download / content-type confusion...