Cookie Does Not Contain The Secure Attribute

cEMa

• June 15, 2017 17:51

Hey everyone, In order to pass PCI Compliance, I need to enable Header always edit Set-Cookie (.*) "$1; HTTPOnly; Secure" on the WHM/cPanel ports 2082,2086,2087,2095. Placing this rule in the httpd conf broke a number of websites, so I've been individually adding it to each site using their .htaccess file. However, the PCI compliance scan detected the above ports as well. [LIST]

Is this a false positive?

If not, how can I apply this rule to only WHM/cPanel ports mentioned above? Any insight would be greatly appreciated. Sincerely, Chase M.

• 

  tank

  • June 15, 2017 23:49

  I would not ever store credit cards on your server if you can help it. Most credit card processors have way for tokens to be used and other methods. Just my two cents. Take a look at the fees for credit cards that are stolen from your server. It is very steep. I hope some else can help you find and solve your problem. Just my two cents.

  0
• 

  cEMa

  • June 16, 2017 00:10

  Thanks for the reply, tank. I would like to enforce this in the httpd conf, since every domain uses the free ssl certificate we provide; however, it breaks the checkout process of another domain (not sure why), causing me to resort to placing the rule in the domains .htaccess file. Anyone else got ideas?

  0
• 

  cEMa

  • June 16, 2017 02:35

  I was able to resolve this by changing the Home > Service Configuration > Apache Configuration > Include Editor > Pre Main Include > All Versions From:
  Header always edit Set-Cookie (.*) "$1; HTTPOnly; Secure"
  To:
  Header edit Set-Cookie ^(.*)$ $1; HttpOnly; Secure
  

  0
• 

  cPanelMichael

  • June 16, 2017 16:42

  Hello, I'm happy to see you were able to address the issue. Thank you for updating us with the outcome.

  0
• 

  Heena H Thakkar

  • April 03, 2018 10:47

  Hey I am still not able to fix above issue. Can you please help me? Vulnerability Detection Result The cookies:
  Set-Cookie: Horde=***replaced***; HttpOnly; domain=.www.abc.com; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; port=2096 Set-Cookie: horde_secret_key=***replaced***; HttpOnly; domain=.www.abc.com; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; port=2096
  are missing the "secure" attribute.

  0
• 

  cPanelMichael

  • April 03, 2018 14:37

  Hello @Heena H Thakkar, As I understand, the "unsecure cookie" message for Horde over port 2096 is a false positive as long as the "Require SSL for cPanel Services" option is enabled under the "Security" tab in "WHM >> Tweak Settings". Thank you.

  0
• 

  Heena H Thakkar

  • April 04, 2018 03:45

  Hi, This is also not helping . Scan results shows same for 3 ports.

  0
• 

  Heena H Thakkar

  • April 04, 2018 07:04

  Vulnerability Detection Result The cookies: Set-Cookie: Horde=***replaced***; HttpOnly; domain=.abc.com; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; port=2096 Set-Cookie: horde_secret_key=***replaced***; HttpOnly; domain=.abc.com; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/; port=2096 are missing the "secure" attribute. This above is for two ports 2096/2083. I tried everything given above, still vulnerability scan gives such results.

  0
• 

  cPanelMichael

  • April 04, 2018 15:27

  Hello, Have you reported this as a false positive to the vendor? I understand this to be a false positive as long as the "Require SSL for cPanel Services" option is enabled under the "Security" tab in "WHM >> Tweak Settings". Thank you.

  0

Please sign in to leave a comment.