You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The url that gets requested here is attacker controlled, with the exception of a forced .jpg being added on meaning they could request local content from 127.0.0.1 for example. I'm not actually sure where this view is used, but mitigations could be either only passing along the image ID (like photo-1547656807-9733c2b738c2) which gets appended to https://images.unsplash.com/ or check that the domain is Unsplash. You should also probably use allow_redirects=False to prevent any open redirects leading to SSRFs.
The text was updated successfully, but these errors were encountered:
Reporting in the public because this got added 1 hour ago and I don't believe this site is deployed publicly.
I'm pretty sure #93 adds an SSRF vulnerability in the
addUnsplashPicture
handler here:The url that gets requested here is attacker controlled, with the exception of a forced
.jpg
being added on meaning they could request local content from127.0.0.1
for example. I'm not actually sure where this view is used, but mitigations could be either only passing along the image ID (likephoto-1547656807-9733c2b738c2
) which gets appended tohttps://images.unsplash.com/
or check that the domain is Unsplash. You should also probably useallow_redirects=False
to prevent any open redirects leading to SSRFs.The text was updated successfully, but these errors were encountered: