apache2 (2.4.65-4) unstable; urgency=medium

  Apache2's integration with systemd has been improved,
  and several hardening flags have been preconfigured for
  its services.
  .
  ProtectHome is set to read-only by default.
  As a result, CGI scripts executed via UserDir will not
  be able to modify any content within the /home directory.
  Additionally, WebDAV write access to /home will also be
  disabled by default. Read-write access may be enabled
  by overriding this setting, following a thorough
  risk assessment.
  Additionally, the libapache2-mpm-itk module may be
  considered, particularly in scenarios that require
  per-user process isolation. libapache2-mpm-itk
  allows Apache to run each virtual host or script
  under a separate Unix user and group ID, thereby
  enhancing security by limiting the impact of potential
  vulnerabilities and preventing unauthorized access
  between users. However, its use should be carefully
  evaluated, taking into account potential performance overhead,
  compatibility with other Apache modules, and the findings of
  a thorough risk assessment.
  .
  KeyringMode is set to private by default, which means
  Apache receives its own isolated kernel keyring.
  While this enhances security by preventing unintended key
  sharing, it can break interoperability if Apache needs
  to exchange keys with other services, for example,
  a backend authentication daemon.
  In such cases, it is recommended to share the keyring using
  an intermediate daemon that securely mediates access
  between processes.
  .
  PrivateDevices is set to yes by default;
  If Apache modules or scripts require access to specific
  devices (using hardware crypto modules, or
  interacting directly with webcams), this setting could break
  functionality.  In such cases, it is advisable to expose
  the required devices through a proxy or an agent service.
  In case of CGI modules, it is recommended to use FCGI modules instead,
  with tailored security hardening.
  .
  MemoryDenyWriteExecute is set to yes by default.
  While this enhances security by preventing writable and
  executable memory regions, it may cause issues with modules
  that rely on JIT engines, such as mod_php with JIT-enabled
  PHP, mod_lua, or custom interpreters. In such cases,
  it is recommended to use PHP-FPM or FCGI modules instead.
  .
  ProtectSystem is set to full by default;
  this mounts various system paths like /usr, /boot and
  /etc as read-only, enhancing overall system integrity.
  .
  Some paths were also made inaccessible, including /boot, /root, /etc/apt
  /etc/ssh, and /etc/sudoers*. This may cause certain CGI scripts to fail.
  In such cases, it is recommended to use FCGI modules instead,
  with tailored security hardening.
  .
  Other hardening flags, including DevicePolicy=closed,
  ProtectClock=yes, LockPersonality=yes, ProtectControlGroups=yes,
  ProtectHostname=yes, ProtectKernelLogs=yes, ProtectKernelModules=yes,
  RestrictNamespaces=yes, RestrictRealtime=yes, and
  SystemCallArchitectures=native, RestrictSUIDSGID=yes,
  ProtectProc=invisible, ProcSubset=pid, RemoveIPC=yes
  are generally safe to enable
  and unlikely to cause compatibility problems.
  .
  If you need to override these defaults, you can do
  so by running:
  "sudo systemctl edit apache2.services" or
  "sudo systemctl edit apache2@.services".
  These commands create a drop-in override file located at:
  /etc/systemd/system/<unit-name>.d/override.conf
  Alternatively, you can create or manage this file directly
  using Ansible or other administrative tooling to automate
  configuration changes.

 -- Bastien Roucariès <rouca@debian.org>  Thu, 14 Aug 2025 13:53:43 +0200

apache2 (2.4.65-3) unstable; urgency=medium

  The default LANG environment variable used by Apache,
  and consequently inherited by WebDAV, PHP and certain CGI scripts,
  has been changed from LANG=C (ASCII) to LANG=C.UTF-8 (UTF-8 Unicode).
  .
  The default setting may be changed by modifying the file
  /etc/apache2/envvars, and restarting apache2 related process.
  .
  This modification may cause compatibility issues
  in programs or modules that are not designed to handle locale
  settings.
  .
  In some cases, it may be necessary to rebuild database indexes to
  ensure proper character encoding and sorting behavior, particularly
  when transitioning from ASCII-based collation to UTF-8,
  which may interpret and order characters differently.

 -- Bastien Roucariès <rouca@debian.org>  Fri, 01 Aug 2025 22:19:44 +0200

apache2 (2.4.65-2) unstable; urgency=medium

  Following the resolution of CVE-2025-23048,
  some SSL-enabled websites may begin encountering
  the error (AH02032):
  .
    Misdirected Request:
    The client needs a new connection for this request as the
    requested host name does not match the Server Name Indication
    (SNI) in use for this connection.
  .
  This behavior is particularly noticeable with AWS Application
  Load Balancers. Although they support intelligent SNI handling,
  they do not (as of this writing) relay SNI data to the target
  server, resulting in failed connections when hostnames don’t align.
  .
  Without an SNI provided by the client, there is nothing httpd
  can do to determine which vhost/configuration should be
  used to provide the correct certificate (and TLS authentication
  eventually) whenever multiple vhosts listen on the same IP:port.
  .
  That's because reading the HTTP Host header necessarily has to
  happen after the TLS handshake/auth/decryption (and later
  renegotiation is not an option with TLSv1.3).
  .
  So those connections fall back to the first vhost declared on
  the IP:port for the TLS handshake part, and if the request
  Host header finally matches a different vhost with a different
  TLS configuration it's rejected with AH02032.
  .
  Before 2.4.64 the check was not accurate and would allow that,
  with security implications.
  .
  As a workaround, you may (after a risk analysis) generate a
  wildcard certificate. If you’re managing multiple domains,
  consolidate them into a single certificate by including each
  wildcard domain as an alias. Then, update the Apache configuration
  to reference this unified certificate.
  .
  Another possible workaround is to configure each virtual host to
  listen on a separate port. This approach avoids SNI-related issues
  by ensuring that each vhost is uniquely addressed through its own
  connection endpoint, thereby allowing distinct TLS configurations
  without ambiguity.
  .
  This error may also stem from a misconfigured HAProxy setup.
  In such cases, enabling dynamic SNI handling on HAProxy might be
  necessary to ensure that the correct hostname is passed through
  during the TLS handshake. After risk analysis, it could be done
  by using "sni req.hdr(Host)" directive.
  .
  This error may also be caused by a misconfigured Nginx proxy setup.
  In such scenarios, enabling Server Name Indication (SNI) when connecting
  to the backend may be necessary to ensure that the correct hostname is
  transmitted during the TLS handshake. After conducting a risk analysis,
  this can be achieved by configuring the "proxy_ssl_server_name on;"
  and "proxy_ssl_name $host;" directives.

 -- Bastien Roucariès <rouca@debian.org>  Fri, 25 Jul 2025 20:33:38 +0200

apache2 (2.4.64-2) unstable; urgency=medium

  RFC 8996 published by the IETF in March 2021,
  mandates the formal deprecation of Transport
  Layer Security (TLS) versions 1.0 and 1.1 due
  to significant security vulnerabilities and limitations.
  These older protocols lack support for modern cryptographic
  algorithms and are prone to exploits that threaten data
  confidentiality and integrity. In alignment with RFC 8996,
  we disable by default these protocols.
  .
  This change can cause older applications or systems
  to break if they haven't been updated to support
  TLS 1.2 or 1.3.

 -- Bastien Roucariès <rouca@debian.org>  Thu, 17 Jul 2025 18:03:42 +0200
