Server-Side Request Forgery (SSRF) Affecting apache2-dev package, versions <2.4.64-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
1.1% (62nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-APACHE2DEV-13313127
  • published6 Oct 2025
  • disclosed10 Jul 2025

Introduced: 10 Jul 2025

CVE-2024-43394  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade Minimos:latest apache2-dev to version 2.4.64-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream apache2-dev package and not the apache2-dev package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Server-Side Request Forgery (SSRF) in Apache HTTP Server on Windows allows to potentially leak NTLM hashes to a malicious server via  mod_rewrite or apache expressions that pass unvalidated request input.

This issue affects Apache HTTP Server: from 2.4.0 through 2.4.63.

Note:  The Apache HTTP Server Project will be setting a higher bar for accepting vulnerability reports regarding SSRF via UNC paths.

The server offers limited protection against administrators directing the server to open UNC paths. Windows servers should limit the hosts they will connect over via SMB based on the nature of NTLM authentication.

CVSS Base Scores

version 3.1