this post was submitted on 07 Apr 2024
117 points (99.2% liked)
Cybersecurity
5973 readers
210 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected]
Notable mention to [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm still learning Cybersec in general, if I'm reading this right, were these credentials hardcoded in by D-Link, these devices reached EOL, and so they refuse to remove that backdoor on the basis that the devices are EOL?
Is there a likely reason that these were left in, like could it have been a development oversight, or does it look more likely that this was malicious?
Regardless, I definitely hold the opinion that D-Link should do the right thing for their customers and patch that vulnerability, regardless of the device being EOL, similar to how Microsoft pushed a security update to Windows XP re WannaCry when it was EOL, on the basis that "Yes, XP is unsupported and you shouldn't use it, but we are patching this particular vulnerability anyway."
D-Link suck, they probably just overlooked it. Consumer-grade router manufacturers generally have abysmal/terrifying software QA. One prominent reason I recommend picking up hardware that supports an open router firmware.