[users@httpd] pipe logs to somethings that resembles a curl post

[Marc]

I was wondering how I could use piped logs to redirect some logs, comparable to 
curl post requests. 

[1]
https://httpd.apache.org/docs/current/logs.html

RE: [users@httpd] Re: Apache server v2.4.58 - suexec issue

[j...@k6ccc.org]

2.4.59 was released a few days ago to address these...

Jim




-Original Message-
From: "Christophe JAILLET" 
Sent: Monday, April 8, 2024 13:26
To: users@httpd.apache.org, "Abdullah Adnan" 
Subject: [users@httpd] Re: Apache server v2.4.58 - suexec issue

Le 07/04/2024 à 19:55, Abdullah Adnan a écrit :
> Good day dears,
> 
> Recently we have installed Apache server v2.4.58 in our CentOS 9, when 
> make vulnerability scan with Nessus on the server the Nessus shows this 
> vulnerability:
> 
> The remote host appears to be running Apache and is potentially
> 
> affected by the following vulnerabilities:
> 
>    - Multiple race conditions exist in suexec between the
> 
>      validation and usage of directories and files. Under
> 
>      certain conditions local users are able to escalate
> 
>      privileges and execute arbitrary code through the
> 
>      renaming of directories or symlink attacks.
> 
>      (CVE-2007-1741)
> 
>    - Apache's suexec module only performs partial
> 
>      comparisons on paths, which could result in privilege
> 
>      escalation. (CVE-2007-1742)
> 
>    - Apache's suexec module does not properly verify user
> 
>      and group IDs on the command line. When the '/proc'
> 
>      filesystem is mounted, a local user can utilize suexec
> 
>      to escalate privileges. (CVE-2007-1743)
> 
> Note that this plugin only checks for the presence of Apache, and does
> 
> not actually check the configuration.

Hi,

looking at theses CVE, they all include "the vendor disputes the issue 
because "the attacks described rely on an insecure server configuration" 
in which the user "has write access to the document root.""

So considering them as security issues is up to you.

> 
> So we need your support to disable suexec in the server.

Disabling a module in Apache looks like a really basic task.
(just comment the corresponding line in the conf file)

CJ

> 
> Thanks,
> 
> Best regards
> 
>   
> 
> *Abdullah Adnan *
> 
> *IT System Administrator|**Arab Payment Services*
> 
> Mobile:   00964-7735387734
> 
> Ext.:   74
> 
> Email: a.ad...@aps.iq 
> 
> Skype:  Abdullah Adnan
> 
> Website: www.aps.iq 
> 
> Address:Iraq *| *Baghdad*| *Abu Nuwas*| *District (102) *|*Street (26) 
> *|*BLDG.(13/66)
> 


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

[users@httpd] Re: Apache server v2.4.58 - suexec issue

[Christophe JAILLET]

Le 07/04/2024 à 19:55, Abdullah Adnan a écrit :

Good day dears,

Recently we have installed Apache server v2.4.58 in our CentOS 9, when 
make vulnerability scan with Nessus on the server the Nessus shows this 
vulnerability:


The remote host appears to be running Apache and is potentially

affected by the following vulnerabilities:

   - Multiple race conditions exist in suexec between the

     validation and usage of directories and files. Under

     certain conditions local users are able to escalate

     privileges and execute arbitrary code through the

     renaming of directories or symlink attacks.

     (CVE-2007-1741)

   - Apache's suexec module only performs partial

     comparisons on paths, which could result in privilege

     escalation. (CVE-2007-1742)

   - Apache's suexec module does not properly verify user

     and group IDs on the command line. When the '/proc'

     filesystem is mounted, a local user can utilize suexec

     to escalate privileges. (CVE-2007-1743)

Note that this plugin only checks for the presence of Apache, and does

not actually check the configuration.


Hi,

looking at theses CVE, they all include "the vendor disputes the issue 
because "the attacks described rely on an insecure server configuration" 
in which the user "has write access to the document root.""


So considering them as security issues is up to you.



So we need your support to disable suexec in the server.


Disabling a module in Apache looks like a really basic task.
(just comment the corresponding line in the conf file)

CJ



Thanks,

Best regards



*Abdullah Adnan *

*IT System Administrator|**Arab Payment Services*

Mobile:   00964-7735387734

Ext.:   74

Email: a.ad...@aps.iq 

Skype:  Abdullah Adnan

Website: www.aps.iq 

Address:Iraq *| *Baghdad*| *Abu Nuwas*| *District (102) *|*Street (26) 
*|*BLDG.(13/66)





-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

[users@httpd] Request for Assistance: Apache mod_slotmem_shm POC

[Sarkar Tarun Kumar (ETAS-SEC/XPC-Bo1)]

Dear Members,

I hope this email finds you well. I am currently working on a Proof of Concept 
(POC) project where I aim to utilize Apache's mod_slotmem_shm module for 
caching data in the shared memory of Apache and subsequently accessing this 
cached data across all Apache workers. However, I have encountered some 
challenges and would greatly appreciate your assistance in resolving them.

Specifically, I am attempting to implement the functionalities described in the 
mod_slotmem_shm documentation found at the following link: 
https://httpd.apache.org/docs/trunk/mod/mod_slotmem_shm.html

My objective is to create a POC that demonstrates the effective caching of data 
within Apache shared memory and its retrieval across multiple Apache worker 
processes.

I have already reviewed the documentation provided by Apache, but I am facing 
difficulties in correctly implementing the functionality in my environment.

Below are some specific areas where I am seeking assistance:


  1.  Initialization and configuration of mod_slotmem_shm within Apache.
  2.  Writing code to cache data in the shared memory using mod_slotmem_shm.
  3.  Retrieving cached data from the shared memory across multiple Apache 
worker processes.

If any of you have experience or expertise in working with mod_slotmem_shm or 
have implemented similar solutions in the past, I would greatly appreciate any 
guidance, code examples, or best practices that you can share.

Additionally, if there are any specific configurations, considerations, or 
potential pitfalls that I should be aware of when working with mod_slotmem_shm, 
I would be grateful for your insights.

Thank you very much for taking the time to read this email, and I look forward 
to any assistance or advice you can provide.

Mit freundlichen Grüßen / Best regards

Tarun Kumar Sarkar

Cross-Functional People and Competence - People Lead Bochum (ETAS-SEC/XPC-Bo1)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | 
www.bosch.com
Tel. +49 234 43870-308 | Mobile +49 172 6994124 | Fax +49 234 43870-211 | 
tarunkumar.sar...@etas.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 
14000;
Chairman of the Supervisory Board: Prof. Dr. Stefan Asenkerschbaumer;
Managing Directors: Dr. Stefan Hartung, Dr. Christian Fischer, Dr. Markus 
Forschner,
Stefan Grosch, Dr. Markus Heyn, Dr. Frank Meyer, Dr. Tanja Rückert
​