Cybersecurity

6571 readers

19 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

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 2 years ago

MODERATORS

kid@sh.itjust.works

Lanky_Pomegranate530@midwest.social

184

Undocumented backdoor found in Bluetooth chip used by a billion devices (www.bleepingcomputer.com)

submitted 1 day ago* (last edited 1 day ago) by neme@lemm.ee to c/cybersecurity@sh.itjust.works

32 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] olafurp@lemmy.world 3 points 1 day ago (1 children)

Couldn't they just designate them as no-op codes?

[–] dave@feddit.uk 13 points 1 day ago

Yes, but to do that they have to be decoded and handled. That's basically what the commenter above was saying.

The original 6502 had many undocumented opcodes for this reason, and developers stated exploiting them for various reasons. The CMOS 65C02 redefined them to no-op. This has been going on a long time.