Skip to main content

PCI compliance test passes on port 443, but fails on ports 2087, 2083, 2096 and 2078

Comments

3 comments

  • cPanelMichael
    Hello :) Are you able to use an alternate PCI scan that lists specific reasons for test failures? For instance, I do not see any references to specific CVE reports or specific attack vectors. Here is a third-party URL to an alternate PCI scan that describes how to manually check if anonymous authentication is possible:
    0
  • MacPhotoBiker
    Hi Michael, thanks for pointing out that I should rather a different scanner :) I just did, and I received the following two vulnerabilities: 1) rsh Service Detection rsh (8889/tcp) CVE-1999-0651 2)OpenSSH < 5.7 Multiple Vulnerabilities ssh (2516/tcp) CVE-2010-4478, CVE-2012-0814 I'm running a VPS on Centos 6.5. Couldyou guide me in the right direction to solve these issues? Thanks a lot!
    0
  • cPanelMichael
    Hello :) It's likely reporting false positives based on the version number in cases where patches have been backported, or in cases where it does not effect the version shipped with your OS. RSH is not a standard package so you could remove it using your system package manager (YUM) if you have no specific requirement for it. CentOS 6 should not be effected by the OpenSSH CVE reports referenced: In both cases it states: Not vulnerable. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 4, 5, or 6. Thank you.
    0

Please sign in to leave a comment.