Issues that might arise due to having content disposition inline on images

Avatar

Avatar
Ignite 1
Level 1
aemAmateur
Level 1

Likes

0 likes

Total Posts

11 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
Validate 1
View profile

Avatar
Ignite 1
Level 1
aemAmateur
Level 1

Likes

0 likes

Total Posts

11 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
Validate 1
View profile
aemAmateur
Level 1

21-02-2021

I have already asked the same question before on the forum, sorry for posting again. l asked the following question.

 

"I am trying to display images (png, jpeg, gif, svg) directly on browser instead of letting the users downloading it. I've read from so many places that having content disposition header as inline might cause some security issues, and it is better to have it as attachment. Can anyone provide me a scenario where this might be a problem?"

 

From the answers from my previous post, I could see mostly the security issue are caused when a malicious attacker injects a script along with the image. Can we tackle this problem by adding a Content-Security-Policy script-src 'none'? my use case for this question only requires the displaying of the image on browser window, and nothing else.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
MVP
raj_mandalapu
MVP

Likes

125 likes

Total Posts

203 posts

Correct reply

72 solutions
Top badges earned
Validate 1
Contributor
Shape 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
MVP
raj_mandalapu
MVP

Likes

125 likes

Total Posts

203 posts

Correct reply

72 solutions
Top badges earned
Validate 1
Contributor
Shape 1
Give Back 5
Give Back 3
View profile
raj_mandalapu
MVP

22-02-2021

@aemAmateur the file which contains executable code is recommended to be downloaded, for example XML, SVG, txt, etc. let us take a simple use case, usually, we use a .svg file to render the images, but at the same time, you can also execute javascript within the SVG file. The problem with this is if you open the SVG within the browser then there is a chance that the attackers can run malicious code in the browser. 

In this case, you need to set the correct mime type that is image/svg+xml and also use  Content-Security-Policy: script-src ‘none’ to disable the javascript execution while loading the SVG file in the browser.

It is good that create and upload .svg file only from the developers. if you give it to the end-user or content authors then you need to set up proper governance and everything should be reviewed and approved.

 

 

 

Answers (1)

Answers (1)

Avatar

Avatar
Validate 10
MVP
kunal23
MVP

Likes

166 likes

Total Posts

565 posts

Correct reply

173 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 50
View profile

Avatar
Validate 10
MVP
kunal23
MVP

Likes

166 likes

Total Posts

565 posts

Correct reply

173 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 50
View profile
kunal23
MVP

21-02-2021

You can add img-src attribute in CSP header to reliably load images from trusted domains only. 

 

For more details, please see this - https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP