Original Message:
Sent: Wed December 03, 2025 03:32 AM
From: Unix Team
Subject: The vulnerability is related to http on port 80 and port 80 runs httpd process from apache
Hello Jose,
Can you please share steps to configure server to use https instead of http.
------------------------------
Unix Team
Original Message:
Sent: Tue December 02, 2025 11:13 AM
From: José Pina Coelho
Subject: The vulnerability is related to http on port 80 and port 80 runs httpd process from apache
There is no "httpd" vendor. Follow the instructions they've given you:
Customers are advised to set proper <a href=""https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options"" target=""_blank"" rel=""noopener noreferrer nofollow"">X-Content-Type-Options</a> and <a href=""https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security"" target=""_blank"" rel=""noopener noreferrer nofollow"">Strict-Transport-Security</a> HTTP response headers.</p><p>
Note that to set Strict-Transport-Security, you need to configure your server to use https instead of http.
------------------------------
José Pina Coelho
IT Specialist at Kyndryl
Original Message:
Sent: Mon December 01, 2025 08:06 AM
From: Unix Team
Subject: The vulnerability is related to http on port 80 and port 80 runs httpd process from apache
Hello Reshma Kumar,
Can we have update on this please. Need to mitigate this issue ASAP.
------------------------------
Unix Team
Original Message:
Sent: Fri November 28, 2025 11:28 AM
From: Unix Team
Subject: The vulnerability is related to http on port 80 and port 80 runs httpd process from apache
Hello Reshma Kumar,
We can update the httpd version to the latest, but does it requires reboot the server?
Also, we couldn't find the remediation steps provided in vulnerability report... Mentioned as to contact vendor as highlighted below. Please find below.
Please share steps to fix the issue.
=============
Remediation Notes:
"<b>Note:</b> To better debug the results of this QID, it is requested that customers execute commands to simulate the following functionality: curl -lkL --verbose.<p>
CWE-693: Protection Mechanism Failure mentions the following - The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. A "missing" protection mechanism occurs when the application does not define any mechanism against a certain class of attack. An "insufficient" protection mechanism might provide some defenses - for example, against the most common attacks - but it does not protect against everything that is intended. Finally, an "ignored" mechanism occurs when a mechanism is available and in active use within the product, but the developer has not applied it in some code path.</p><p>
Customers are advised to set proper <a href=""https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options"" target=""_blank"" rel=""noopener noreferrer nofollow"">X-Content-Type-Options</a> and <a href=""https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security"" target=""_blank"" rel=""noopener noreferrer nofollow"">Strict-Transport-Security</a> HTTP response headers.</p><p>
Depending on their server software, customers can set directives in their site configuration or Web.config files. Few examples are:</p><p>
X-Content-Type-Options:<br />
Apache: Header always set X-Content-Type-Options: nosniff</p><p>
HTTP Strict-Transport-Security:<br />
Apache: Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"<br />
Nginx: add_header Strict-Transport-Security max-age=31536000;</p><p>
<b>Note: Network devices that include a HTTP/HTTPS console for administrative/management purposes often do not include all/some of the security headers. This is a known issue and it is recommend to contact the vendor for a solution. </b></p><p></p>"
------------------------------
Unix Team
Original Message:
Sent: Fri November 21, 2025 07:01 AM
From: RESHMA KUMAR
Subject: The vulnerability is related to http on port 80 and port 80 runs httpd process from apache
Based on the details shared, this looks like a server configuration issue. Please make the required changes as per the remediation steps provided, restart the server and try again.
Additionally, the version of httpd installed is old, so please update it to the latest version(ie, 2.4.65) using "dnf update httpd"
------------------------------
RESHMA KUMAR
Original Message:
Sent: Thu November 20, 2025 03:06 AM
From: Unix Team
Subject: The vulnerability is related to http on port 80 and port 80 runs httpd process from apache
Hello Reshma Kumar,
Please find the output of asked command and Vulnerability reported details.
gdisprnimal1d(root):/# rpm -qi httpd
Name : httpd
Version : 2.4.54
Release : 3
Architecture: ppc
Install Date: Tue Aug 8 10:52:24 CEST 2023
Group : System Environment/Daemons
Size : 14545732
License : Apache Software License
Signature : (none)
Source RPM : httpd-2.4.54-3.src.rpm
Build Date : Fri Oct 21 11:36:00 CEST 2022
Build Host : pokndd5.pok.stglabs.ibm.com
Relocations : /opt /var /etc
Packager : IBM AIX Toolbox <https://ibm.biz/AIXToolbox>
URL : http://httpd.apache.org/
Bug URL : https://ibm.biz/aixoss_forum
Summary : Apache HTTP Server
Description :
The Apache HTTP Server is a powerful, efficient, and extensible
web server.
gdisprnimal1d(root):/#
Vulnerability Details:
| Summary |
| HTTP Security Header Not Detected |
| Remediation notes |
<b>Note:</b> To better debug the results of this QID, it is requested that customers execute commands to simulate the following functionality: curl -lkL --verbose.<p> CWE-693: Protection Mechanism Failure mentions the following - The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. A "missing" protection mechanism occurs when the application does not define any mechanism against a certain class of attack. An "insufficient" protection mechanism might provide some defenses - for example, against the most common attacks - but it does not protect against everything that is intended. Finally, an "ignored" mechanism occurs when a mechanism is available and in active use within the product, but the developer has not applied it in some code path.</p><p> Customers are advised to set proper <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options" target="_blank" rel="noopener noreferrer nofollow">X-Content-Type-Options</a> and <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security" target="_blank" rel="noopener noreferrer nofollow">Strict-Transport-Security</a> HTTP response headers.</p><p> Depending on their server software, customers can set directives in their site configuration or Web.config files. Few examples are:</p><p> X-Content-Type-Options:<br /> Apache: Header always set X-Content-Type-Options: nosniff</p><p> HTTP Strict-Transport-Security:<br /> Apache: Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"<br /> Nginx: add_header Strict-Transport-Security max-age=31536000;</p><p> <b>Note: Network devices that include a HTTP/HTTPS console for administrative/management purposes often do not include all/some of the security headers. This is a known issue and it is recommend to contact the vendor for a solution. </b></p><p></p> |
| Description |
X-Content-Type-Options HTTP Header missing on port 80.
GET / HTTP/1.1 Host: 10.247.138.194 Connection: Keep-Alive User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
HTTP/1.1 200 OK Date: Sat, 01 Nov 2025 17:37:17 GMT Server: Apache/2.4.54 (Unix) Last-Modified: Mon, 11 Jun 2007 18:53:14 GMT ETag: "2d-432a5e4a73a80" Accept-Ranges: bytes Content-Length: 45 Keep-Alive: timeout=5, max=96 Connection: Keep-Alive Content-Type: text/html
<html><body><h1>It works!</h1></body></html> |
------------------------------
Unix Team
Original Message:
Sent: Wed November 19, 2025 04:49 AM
From: RESHMA KUMAR
Subject: The vulnerability is related to http on port 80 and port 80 runs httpd process from apache
Please share the details of the vulnerabilities reported and the output of "rpm -qi httpd".
If mod_ssl rpm is not installed, you can install the same using " dnf install mod_ssl". This will enable ssl module and httpd can listen on port 443.
------------------------------
RESHMA KUMAR
Original Message:
Sent: Mon November 17, 2025 09:22 AM
From: Unix Team
Subject: The vulnerability is related to http on port 80 and port 80 runs httpd process from apache
The vulnerability is related to http on port 80 and port 80 runs httpd process from apache as follows:-
gdisprnimal1d(root):/# lsof -i :80 -w
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
httpd 9240872 root 4u IPv6 0xf10010000a38bbc0 0t0 TCP *:http (LISTEN)
gdisprnimal1d(root):/# ps -ef | grep -i 9240872
root 9240872 1 0 Aug 22 - 0:30 /opt/freeware/sbin/httpd -k start
apache 21692778 9240872 0 Nov 01 - 0:00 /opt/freeware/sbin/httpd -k start
Need help on this to fix http Vulnerability reported on port 80 on Infra NIM servers
------------------------------
Unix Team
------------------------------