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

Issue with cdn-scanner when using a CIDR block #9

Open
luchua-bc opened this issue Jan 29, 2024 · 2 comments
Open

Issue with cdn-scanner when using a CIDR block #9

luchua-bc opened this issue Jan 29, 2024 · 2 comments

Comments

@luchua-bc
Copy link

I'm running cdn-scanner to scan an AWS CIDR block:

cdn-scanner -domain {my_instance}.cloudfront.net cloudfront 3.160.0.0/14

And I got the following:

Ulimit # of files open is currently set to 65326
https://3.160.0.0/14 -- Via Proxy: closed (502), Origin: error (000 -- Get "https://3.160.0.0%2F14/": dial tcp: lookup 3.160.0.0/14: no such host)
http://3.160.0.0/14 -- Via Proxy: closed (502), Origin: error (000 -- Get "http://3.160.0.0%2F14/": dial tcp: lookup 3.160.0.0/14: no such host)

It seems that 3.160.0.0/14 is treated as a single IP instead of a CIDR block. What's the correct command?

Thanks,
Luc

@RyanJarv
Copy link
Owner

RyanJarv commented Apr 5, 2024

@luchua-bc Sorry for the delay here, I don't think the target selection supports CIDRs right now. If you want to expand the IPs out in to a file though it should accept that though.

https://github.com/RyanJarv/cdn-proxy/blob/main/main.go#L232

@luchua-bc
Copy link
Author

Thanks @RyanJarv for confirming the workaround.

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