Security release!

moderate: Apache HTTP Server: HTTP response splitting ( CVE-2023-38709)

Faulty input validation in the core of Apache allows malicious or exploitable backend/content generators to split HTTP responses.

This issue affects Apache HTTP Server: through 2.4.58.

Acknowledgements: finder: Orange Tsai (@orange_8361) from DEVCORE

Reported to security team	2023-06-26
Update 2.4.59 released	2024-04-04
Affects	<=2.4.58

low: Apache HTTP Server: HTTP Response Splitting in multiple modules ( CVE-2024-24795)

HTTP Response splitting in multiple modules in Apache HTTP Server allows an attacker that can inject malicious response headers into backend applications to cause an HTTP desynchronization attack.

Users are recommended to upgrade to version 2.4.59, which fixes this issue.

Acknowledgements:

finder: Keran Mu, Tsinghua University and Zhongguancun Laboratory.
finder: Jianjun Chen, Tsinghua University and Zhongguancun Laboratory.

Reported to security team	2023-09-06
Update 2.4.59 released	2024-04-04
Affects	<=2.4.58

moderate: Apache HTTP Server: HTTP/2 DoS by memory exhaustion on endless continuation frames ( CVE-2024-27316)

HTTP/2 incoming headers exceeding the limit are temporarily buffered in nghttp2 in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion.

Acknowledgements: finder: Bartek Nowotarski (https://nowotarski.info/)

Reported to security team	2024-02-22
Update 2.4.59 released	2024-04-04
Affects	<=2.4.58

Posted: Thu 04 Apr '24 17:05
Post subject: Apache httpd 2.4.59 GA Available

Apache httpd 2.4.59 is released as GA.

ASF and Apachelounge changes : https://www.apachelounge.com/Changelog-2.4.html

Important security vulnerabilities are fixed in 2.4.59, see https://httpd.apache.org/security/vulnerabilities_24.html .

VS17 Win32
The Win32 version is available again, see also discussion https://www.apachelounge.com/viewtopic.php?p=42099
Only build the with the standard Apache modules.
For non-standard modules (like mod_fcgid) use the VS16 Win32 ones at https://www.apachelounge.com/download/VS16/

Documentation: http://httpd.apache.org/docs/2.4/

Build with dependencies:

- openssl 3.1.5
- nghttp2 1.61.0
- jansson 2.14
- curl 8.7.1
- apr 1.7.3
- apr-util 1.6.3
- apr-iconv 1.2.2
- zlib 1.3.1
- brotli 1.1.0
- pcre2 10.43
- libxml2 2.12.6
- lua 5.4.6
- expat 2.5.0

Notes VS17 OpenSSL 3.x.x:

- Only PHP 8.2 and 8.1 (build with 3.x.x) is running as module.
Running with mod_fcgid no issues seen.

For running as module, See also the post from user Otomatic and notes at https://www.apachelounge.com/viewtopic.php?t=8969
and https://www.apachelounge.com/viewtopic.php?t=8938

- With too weak certificates/ciphers Apache does not start, see https://www.apachelounge.com/viewtopic.php?t=8819

Enjoy,

Steffen

Release URL: https://github.com/Bearsampp/module-apache/releases/tag/2024.4.7

Security release!

Wednesday, April 10, 2024 Security Releases

Rafael Gonzaga

Security releases available

Updates are now available for the 18.x, 20.x, 21.x Node.js release lines for the following issues.

Command injection via args parameter of child_process.spawn without shell option enabled on Windows (CVE-2024-27980) - (HIGH)

Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject arbitrary commands and achieve code execution even if the shell option is not enabled.

It is important to note that there has been a breaking change for Windows users who utilize child_process.spawn and child_process.spawnSync. Node.js will now error with EINVAL if a .bat or .cmd file is passed to child_process.spawn and child_process.spawnSync without the shell option set. If the input to spawn/spawnSync is sanitized, users can now pass { shell: true } as an option to prevent the occurrence of EINVALs errors.

While it is possible to also pass --security-revert=CVE-2024-27980 to revert the security patch, we strongly advise against doing so. Impact:

This vulnerability affects all Windows users in active release lines: 18.x, 20.x, 21.x

Thank you, to ryotak for reporting this vulnerability and thank you Ben Noordhuis for fixing it.

Summary

The Node.js project will release new versions of the 18.x, 20.x, 21.x releases lines on or shortly after, Tuesday, April 9, 2024 in order to address:

1 high severity issues.

Impact

The 18.x release line of Node.js is vulnerable to 1 high severity issue. The 20.x release line of Node.js is vulnerable to 1 high severity issue. The 21.x release line of Node.js is vulnerable to 1 high severity issue.

Release timing

Releases will be available on, or shortly after, Tuesday, April 9, 2024.

Contact and future updates

The current Node.js security policy can be found at https://nodejs.org/en/security/. Please follow the process outlined in https://github.com/nodejs/node/blob/master/SECURITY.md if you wish to report a vulnerability in Node.js.

Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the nodejs GitHub organization.

We have multiple releases out for NodeJS to address security issues. These are running on NPM 10.5.0 and it is highly recommended you update to these versions to mitigate the security risk.

Release URL: https://github.com/Bearsampp/module-nodejs/releases/tag/2024.4.11

Security release!

Vulnerabilities

moderate: Apache HTTP Server: HTTP response splitting ( CVE-2023-38709)

low: Apache HTTP Server: HTTP Response Splitting in multiple modules ( CVE-2024-24795)

moderate: Apache HTTP Server: HTTP/2 DoS by memory exhaustion on endless continuation frames ( CVE-2024-27316)

Changelog

Release Files