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

No CSS files were found? #21

Closed
marcelo321 opened this issue Jun 19, 2024 · 7 comments
Closed

No CSS files were found? #21

marcelo321 opened this issue Jun 19, 2024 · 7 comments

Comments

@marcelo321
Copy link

Do we hae to link CSS files, or how does one see how the tool performs CSS poisoning, how it differs from the other tests?

@Sh4d0wHunt3rX
Copy link

Hey @marcelo321 , did you find this out? It's first time I'm running this and got this:

image

@m10x
Copy link
Collaborator

m10x commented Sep 8, 2024

Do we hae to link CSS files, or how does one see how the tool performs CSS poisoning, how it differs from the other tests?

WCVS searches responses for linked CSS files. It is not possible to directly link CSS files. CSS files are mostly static but there may be occasions where CSS files reflect the requests URL. WCVS checks if that is the case and if true whether it's possible to poison the cache with an arbitrary URL. That is the only check for CSS files.

@m10x
Copy link
Collaborator

m10x commented Sep 8, 2024

Hey @marcelo321 , did you find this out? It's first time I'm running this and got this:

image

The website you are scanning returns Cf-Cache-Status: DYNAMIC. This means, that the response is not eligible for caching. Hence, wcvs will not test for web cache poisoning (unless you force it to with -f/-force). However, it is trying to achieve web cache deception. This means that it is trying to manipulate the request in order for the response to get cached. It is doing this by trying to trick the Cache Proxy into thinking that a css files is requested. That is because css files will be cached most of the times. The status codes 400 and 444 mean that the Cache Proxy could not be tricked.

@Sh4d0wHunt3rX
Copy link

@m10x Thank you so much for your great explanation and the tool 🙏

@schooldropout1337
Copy link

schooldropout1337 commented Oct 24, 2024

InShot_20241024_145331625

Getting this error on android (termux)

termux-tools version: 1.38.3
Android version: 11
Kernel build info: Linux localhost 4.9.227-perf+ #1 SMP PREEMPT Wed Mar 16 16:56:21 CST 2022 aarch64 Android

@m10x
Copy link
Collaborator

m10x commented Oct 24, 2024

Golang throws an error because https://example.com% is an invalid format and it won't send the request. https://example.com/% however would be rfc compliant and work.

@schooldropout1337
Copy link

Thanks m8, got it. '/' trailing was missing.

@m10x m10x closed this as completed Dec 21, 2024
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