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

phpipam 1.2 - Multiple Cross-Site Scripting (XSS) #992

Closed
bestshow opened this issue Feb 27, 2017 · 4 comments
Closed

phpipam 1.2 - Multiple Cross-Site Scripting (XSS) #992

bestshow opened this issue Feb 27, 2017 · 4 comments

Comments

@bestshow
Copy link

bestshow commented Feb 27, 2017

Product:phpipam
Download: https://github.com/phpipam/phpipam
Vunlerable Version: 1.2 and probably prior
Tested Version: 1.2
Author: ADLab of Venustech

Advisory Details:
I have discovered multiple Cross-Site Scripting (XSS) in “phpipam”, which can be exploited to execute arbitrary code.
The vulnerability exists due to insufficient filtration of user-supplied data in multiple HTTP POST parameters passed to several pages. An attacker could execute arbitrary HTML and script code in a browser in the context of the vulnerable website.
The exploitation examples below use the "alert()" JavaScript function to see a pop-up messagebox:
Poc:
(1)
Post : instructions = ><script>alert(1);</script><
To
http://localhost/github1/.../phpipam-master/app/admin/instructions/preview.php

(2)
Post : subnetId = ><script>alert(1);</script><
To
http://localhost/github1/.../phpipam-master/app/admin/powerDNS/refresh-ptr-records.php

@bestshow bestshow changed the title phpipam (lastest version)- Multiple Cross-Site Scripting (XSS) phpipam 1.2 - Multiple Cross-Site Scripting (XSS) Mar 2, 2017
@phpipam
Copy link
Owner

phpipam commented Mar 3, 2017

This is fixed in latest master version, thanks anyway.

@phpipam phpipam closed this as completed Mar 3, 2017
@attritionorg
Copy link

91fb8e3 takes care of the first one, and more. But that doesn't mention refresh-ptr-records.php. Can you link the fixing commit for that one?

@phpipam
Copy link
Owner

phpipam commented Mar 8, 2017

Added fix for second parameter.

@vancluever
Copy link
Contributor

Hey @phpipam, if 1.3 is still a bit out, can we get this back-ported into 1.2 by any chance? Would be good for some extra peace of mind.

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

4 participants