Page tree
Skip to end of metadata
Go to start of metadata

Overview

Most PCI compliance scanning systems are based on a specific version number of a software package that contains a reported vulnerability. This document discusses some of the specific software packages that contain known vulnerabilities. It will also help you determine whether developers used a process known as backporting to patch a software package.

What is backporting?

Backporting allows the operating system vendor to change only the parts of the software that were affected by the security vulnerability. In this way, it avoids the introduction of new features that the developers did not test. This process does not increment the version number. Instead, the developers attach a flag to the package.

Operating system developers often backport updates in order to avoid the need to distribute a new version of the software package.

For example, an operating system developer may combine OpenSSL 0.9.7c with a patch from OpenSSL 0.9.7.d to create OpenSSL 0.9.7c-2. If most PCI scanning systems look for OpenSSL version 0.9.7d or higher, they may incorrectly show OpenSSL 0.9.7c-2 as vulnerable. In this case, you would inform the PCI compliance company that you use a backported version of the software package, which its developers patched for the vulnerability. After you inform them of this, they can record your software version and mark a false positive in the scan results.

OpenSSL

Warning:

You should only replace your OpenSSL installation as a last resort.

Many different system services and packages use OpenSSL. To check your OpenSSL installation for backporting, perform the following steps:

  1. To determine which OpenSSL package is installed on your system, run the following command:

    The output that is similar to the following example indicates that the version of your OpenSSL package is openssl-0.9.8b-10:

  2. To check the RPM change log for vulnerability fixes that that version includes, run the following command:

  3. If the RPM change log includes fixes for the CVEs that your PCI compliance scanning company requires, inform them of the patched version and which CVEs it includes so that they can mark it as a false positive.

OpenSSH

The version of OpenSSH that is currently available via the default repositories is OpenSSH version 5.3.

To determine which OpenSSH package is installed on your system, run the following command:

The output that is similar to the following example indicates that the version of your OpenSSH package is openssh-5.3p1-94.e16:

 This version of OpenSSH may result in a PCI scan that returns the following two vulnerabilities:

  • OpenSSH J-PAKE Session Key Retrieval Vulnerability — This issue does not affect OpenSSH as shipped with RedHat Enterprise Linux 4, 5, and 6. For more information, read CVE-2010-4478 on RedHat's web site.
  • OpenSSH "child_set_env()" Security Bypass Issue —This issue has low impact on security and does not pose a severe risk to most systems. Even though this issue has been addressed in OpenSSH 6.6, this updated version is not yet available in the RedHat repositories. If you wish to update OpenSSH to the new version, you must install it manually.

    Warning

    You should only replace your OpenSSH installation as a last resort. Unless you have a qualified system administrator, do not update your OpenSSH installation. cPanel does not provide support for software that is not yet available in the repositories.

    For information on how to update your OpenSSH software, read this third-party tutorial at ptudor.

mod_frontpage

PCI scans may report the Apache mod_frontpage module as a vulnerability. This is due to a buffer overflow error that may cause privilege escalation, which includes root access. The vulnerability exists in a default Apache installation, but not in cPanel's environment.

A typical scan may provide results that are similar to the following example:

 

If you use EasyApache to build Apache, or if you have never modified your Apache configuration, the fpexe FrontPage binary is configured differently from a default installation:

VersionDescription
Apache 2If you use EasyApache to compile Apache 2.x, the /scripts/fp-auth script replaces fpexe. The /scripts/fp-auth script is never setuid root.

If you build Apache 2 with EasyApache, it does not leave a system vulnerable to the CVE report's exploit. The /scripts/fp-auth script prevents the privilege escalation scenario.

Warning:

We strongly recommend that you do not install FrontPage. The module is no longer supported by any upstream development team and has reached End Of Life. We recommend that you publish content with a different method, such as FTP or WebDAV.

Exim

cPanel & WHM includes patches that help to make Exim PCI compliant. The RPM change log includes information about these patches.

Cipher Keys adjustment

Your PCI compliance scanning software reports which ciphers it permits for use during an encrypted communication. To adjust your cipher keys for PCI Compliance, perform the following steps as the root user:

For Exim, perform the following steps:

  1. Navigate to the Advanced Editor section of WHM's Exim Configuration Manager interface (Home >> Service Configuration >> Exim Configuration Manager).
  2. Enter the following line of code in the tls_require_ciphers text box:

  3. Click Save.

For POP3 or IMAP, perform the following steps:

  1. Navigate to WHM's  Mailserver Configuration  interface (Home >> Service Configuration >> Mailserver Configuration).
  2. Enter the following line of code in the SSL Cipher List text box:

  3. Click Save.

For cPanel Web Services, perform the following steps:

  1. Navigate to WHM's cPanel Web Services Configuration interface (Home >> Service Configuration >> cPanel Web Services Configuration)
  2. Enter the following line of code in the TLS/SSL Cipher List text box:

  3. Click Save.

Simple Mail Transfer Protocol

PCI Compliance requires email client encryption. Your email client provides SSL and TLS encryption. To enable encryption of your SMTP transactions, perform the following steps as the root user:

  1. Navigate to WHM's  Exim Configuration Manager interface (Home >> Service Configuration >> Exim Configuration Manager).
  2. Enable the Require clients to connect with SSL or issue the STARTTLS command before they are allowed to authenticate with the server. option.
  3. Click Save.

Backported CVEs

To view the CVE-related fixes in your version of Exim, run the following command:

 

The output will display the CVE number:

For example, your output may look similar to the following:

 

To report the CVE fixes that your Exim installation includes, send the output that reflects the patched software to the PCI scanning company.

Bind

Although cPanel & WHM does not create BIND, all cPanel servers include BIND by default. Vendor updates will typically resolve PCI compliance issues.

BIND CVE-2011-4313

The BIND change log does not show CVE-2011-4313 directly. Instead, the change log shows under RHEL #754398.

Run the following command to test for the presence of this fix:

Your output should resemble the following example:

 

To report the CVE fixes that your BIND installation includes, send the output that reflects the patched software to the PCI scanning company.

 

Hide the BIND Version

To become PCI compliant, you must hide the BIND version on your server.

To do this, perform the following steps:

  1. Connect to the server via SSH as the root user.
  2. Edit the /etc/named.conf file and add the following line of code to the options section:

  3. Use the following command to restart BIND:

  4. Rescan your server with your account on the PCI company's website.

 

Hide the DNS Server Hostname

To become PCI compliant, you must hide your DNS server’s hostname.

To do this, perform the following steps:

  1. Connect to the server via SSH as the root user.
  2. Edit /etc/named.conf and add the following line of code to the options section:

  3. Use the following command to restart BIND:

  4. Rescan your server with your account on the PCI company's website.

 

Mailman

Mailman can be completely disabled when you scan for PCI Compliance.

To disable Mailman, perform the following steps:

  1. Log in to WHM as the root user.
  2. In the Mail section of the Tweak Settings interface (Home >> Server Configuration >> Tweak Settings), set the Enable Mailman mailing lists setting to Off.
  3. Click Save.

If you do not want to disable Mailman, perform the following steps to pass a PCI Compliance scan:

  1. Connect to the server via SSH as the root user.

  2. Create the following file to deny web requests for Mailman:

    The contents of the file should appear similar to the following example:

  3. Rescan your server with your account on the PCI company's website.
  • No labels