-
Notifications
You must be signed in to change notification settings - Fork 8
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 CNAME record found for:" warning is misleading? #9
Comments
Hey @cherdt, thanks for reporting this! Do you have a concrete example where SubSnipe says that no CNAME exists but one actually does exist? That feels very odd to me. |
I think I'm seeing the issue, the CNAME record exists but points to a FQDN that does not exist. This result makes sense, but I was misinterpreting the results/the message was not necessarily what I was expecting. Here's a concrete example:
but the CNAME value does not exist:
|
Thanks for providing the extra information! I have some other things in the backlog but I will check it out when I have a moment and come back to you. |
I just pulled the latest updates, I'm still getting different results:
It's also interesting to me that there it indicates there are 2 subdomains to check. There is only one subdomain in the input file:
(I've tried both with and without the terminal dot.) I'm running the test on an Ubuntu VM:
Go version is 1.18.1:
|
Hi @cherdt, I spent some time investigating: So the bug with the "2 subdomains" was that I didn't handle new lines in the subdomains file properly in some cases. This is fixed now. For the "CNAME not found" issue: The tool works properly for 'subsnipe.osric.org' when running it inside of a Ubuntu VM for me. It also works within a Ubuntu docker container. However, I was able to replicate the behavior you are experiencing from within the Ubuntu subsystem in Windows. Is that how you run the tool? |
I'm not running it through WSL, but I am running on a Windows machine (via
VirtualBox).
…On Wed, Oct 23, 2024, 8:51 AM Florian Walter ***@***.***> wrote:
Hi @cherdt <https://github.com/cherdt>, I spent some time investigating:
So the bug with the "2 subdomains" was that I didn't handle new lines in
the subdomains file properly in some cases. This is fixed now.
For the "CNAME not found" issue: The tool works properly for '
subsnipe.osric.org' when running it inside of a Ubuntu VM for me. It also
works within a Ubuntu docker container. However, I was able to replicate
the behavior you are experiencing from within the Ubuntu subsystem in
Windows.
Is that how you run the tool?
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC5MBC2HG2N3HQ42ZIUGVTZ46SWNAVCNFSM6AAAAABPTFM73WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZSGI3TKMRSGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I think I figured out the reason for the problem, and it's this: https://stackoverflow.com/questions/56856075/how-can-i-get-the-cname-of-a-host-for-which-dns-resolution-fails-nxdomain-in-g It looks like the standard Go DNS library (which I'm using) returns an error if no A record exists, and then doesn't resolve the CNAME. And as we can see with Now the weird part is: Why does it work on Mac, Linux, etc., but only not on Ubuntu on Windows? It also works on Kali on Windows, and Mint on Windows... but not Ubuntu 😄 |
Will probably check out other DNS libraries and see if that works better. |
@cherdt could you please check out this pull request (#10) and see if it resolves the issue? To do this, navigate into the folder of the git repo and run:
|
When running subsnipe I get a number of warnings like the following:
However, there is a CNAME record for that subdomain, e.g.:
I haven't dug into the logic, but I assume the message indicates that the CNAME record is part of the same domain, and therefore presumably not vulnerable. I just thought it an unusual warning for a case where a CNAME record exists.
The text was updated successfully, but these errors were encountered: