Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

question on the symlinks vunerability

Discussion in 'Security' started by durangod, Jul 20, 2014.

  1. durangod

    durangod Well-Known Member

    Joined:
    May 12, 2012
    Messages:
    441
    Likes Received:
    27
    Trophy Points:
    78
    cPanel Access Level:
    Root Administrator
    It says that the symlinks vulnerability is when you have both followsymlinks and SymLinksIfOwnerMatch turned on (enabled). Well if i just turn SymLinksIfOwnerMatch off (disable) by in apache config, wont that take care of this without having to do all this other stuff im reading about?

    I certainly dont know it all but in my use i have only personally seen and used followsymlinks anyway and i dont think the average user would even know about SymLinksIfOwnerMatch or even use it.


    Would that work?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. cPanelMichael

    cPanelMichael Technical Support Community Manager
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    45,442
    Likes Received:
    1,962
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello :)

    This is addressed on the following thread:

    Solutions for handling symlink attacks

    I've linked to the post where a list of solutions is available. Please direct any questions on the topic to that particular thread.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. quizknows

    quizknows Well-Known Member

    Joined:
    Oct 20, 2009
    Messages:
    1,011
    Likes Received:
    89
    Trophy Points:
    78
    cPanel Access Level:
    DataCenter Provider
    Definitely reference that other thread.

    However, what you WANT is symlinksifownermatch. Normal +followsymlinks is the issue; people can use apache to read other peoples config files without additional security precautions. Even if you disable +followsymlinks, normally users could just re-enable it in their own .htaccess, and many CMSes rely on that being on.

    If you use SuPHP, the "symlink race condition protection" in EasyApache is good enough IMO.
     
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice