Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Directory traversal vulnerability on Windows platform #447

Closed
essen opened this issue Feb 23, 2013 · 4 comments
Closed

Directory traversal vulnerability on Windows platform #447

essen opened this issue Feb 23, 2013 · 4 comments

Comments

@essen
Copy link
Member

essen commented Feb 23, 2013

A directory traversal vulnerability affecting all Windows platforms has been discovered. Please follow these instructions to find out if you are affected. Please take immediate action if you are.

Am I affected?

You are if you match all of the following requirements:

  • You run Cowboy in production on the Windows platform
  • You make use of cowboy_static (or cowboy_http_static in older versions)

How serious is it?

This vulnerability allows an attacker to request any file from your system (only limited by the access rights of the user running the Erlang VM). The attacker cannot list files through this vulnerability. This however does not reduce the seriousness of this vulnerability as an attacker can always use brute force or any other method to try to find files on your system.

How can I fix it?

No patch is currently available.

You should temporarily switch to using IIS or any other web server for serving the static files, or use a CDN instead.

How can I make sure this will not happen again?

A fully cross-platform fix will be pushed to Cowboy in the coming days.

This issue exists essentially because Windows isn't a supported platform and we do not have the resources or knowledge to make the Windows experience safe and smooth.

If you are a Windows user, you can ensure that kind of issue does not happen again by becoming a regular contributor and making sure the team is aware of any potential issue that may arise on Windows.

Why disclose?

Essentially for three reasons:

  • Considering the known user base, a very low number of people might be hit by this issue
  • A temporary fix is readily available
  • Community help is needed to ensure a proper fix gets merged

Please ping this ticket if you are affected. Ignore if you are not. Thanks.

@dvv
Copy link
Contributor

dvv commented Feb 23, 2013

I may test things

@dvv
Copy link
Contributor

dvv commented Feb 23, 2013

@dvv
Copy link
Contributor

dvv commented Feb 25, 2013

another precausion would be to reply with 400/403 for names considered somewhat dangerous -- those containing "..", ":" etc, list to be discussed.

@essen
Copy link
Member Author

essen commented Mar 1, 2013

Fixed. Thanks for the help!

@essen essen closed this as completed Mar 1, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants