Upgrade to the maintenance version that includes the fix for CVE-2021-44228: Follow these steps in your existing ITSI installation to reduce your exposure to the CVE-2021-44228 vulnerability.Ĭloud customers: Splunk Cloud TechOps is upgrading impacted versions.
See the workaround steps provided on this page after this table. ITSI and ITE Work versions 4.11.0, 4.9.x (on-premises and cloud) For more information on addressing the vulnerabilities, see Splunk Security Advisory for Apache Log4j (CVE-2021-44228 and CVE-2021-45046).
The Apache Software Foundation released a series of emergency patches for these vulnerabilities. See Apache Log4j 2 in Apache documentation for more info. Over subsequent days, additional vulnerabilities have been discovered. On Friday December 10, 2021, a serious remote code execution (RCE) vulnerability, commonly known as Log4Shell, was discovered in the popular open-source Apache Log4j (versions 2.0 to 2.14.1) logging library. Refer to the Apache documentation if you require further information.Steps to address the Apache Log4j vulnerabilities in ITSI or IT Essentials Work In general, most problems will be caused by an incorrect setting in the nf configuration file. Step 7: Test the Web serverĬreate a file named index.html in Apache’s web page root (either htdocs or D:\WebPages) and add a little HTML code: Testing Apache Apache is working! Įnsure Apache has started successfully, open a web browser and enter the address If all goes well, your test page should appear. Set the Startup type to “Automatic” to ensure Apache starts every time you boot your PC.Īlternatively, set the Startup type to “Manual” and launch Apache whenever you choose using the command “net start Apache2.4”. Open the Control Panel, Administrative Tools, then Services and double-click Apache2.4. Open a new command prompt as administrator, and enter the following: cd /Apache24/bin The easiest way to start Apache is to add it as a Windows service.
Step 6: install Apache as a Windows service If not, correct any nf configuration errors and retest until none appear. Open a command box (Start > Run > cmd) and enter: # navigate to Apache bin directory cd /Apache24/bin Your Apache configuration can now be tested.
Line 251, set the root: DocumentRoot "D:/WebPages" For the purposes of this example, we’ll create a folder called D:WebPages and change nf accordingly: It’s good to use a folder on an another drive or partition to make backups and re-installation easier. Step 4: Change the Web Page Root (optional)īy default, Apache returns files found in its C:/Apache24/htdocs folder. Line 227, specify the server domain name: ServerName localhost:80 Line 162, enable mod-rewrite by removing the # (optional, but useful): LoadModule rewrite_module modules/mod_rewrite.so Line 60, listen to all requests on port 80: Listen *:80 There are several lines you should change for your production environment: If you installed Apache anywhere other than C:/Apache24, now is a good time to search and replace all references to C:/Apache24. Note that all file path settings use a forward slash ( /) rather than the Windows backslash. Step 4: Configure ApacheĪpache is configured with the text file conf/nf contained in the Apache folder. Apache can be installed anywhere on your system, but you’ll need to change SVROOT configuration to point to your unzipped location - suh as E:/Apache24.
We’ll install Apache in C:/Apache24, so extract the ZIP file to the root of the C:/ drive. You may have this installed already, but there is no harm installing it again.Īs always, remember to virus scan all downloads. However, it’s provided as a manually installable ZIP file from You should also download and install the Windows C++ runtime from. This version has performance and stability improvements over the official Apache distribution, although I’m yet to notice a significant difference. We’re going to use the unofficial Windows binary from Apache Lounge. If you would prefer Apache, either remove IIS as a Windows component or disable its services. If you have a Professional or Server version of Windows, you may already have IIS installed. You need to uninstall or disable any program that uses that port.
Manual installation offers several benefits: