this post was submitted on 05 Jul 2024
208 points (99.1% liked)

Technology

59641 readers
3561 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world -3 points 4 months ago (1 children)

Exactly what this is. Read the disclosure. What about your response doesn't fit that?

[–] NateNate60@lemmy.world 0 points 4 months ago (2 children)

They did not do it by manipulating code. This wasn't the result of a code vulnerability. If you leave the door wide open with all your stuff out for the entire neighbourhood to see, you can't claim you were "broken into". Similarly, if you don't secure your endpoints, you can't claim you were "hacked".

[–] sudneo@lemm.ee 1 points 4 months ago (1 children)

Lack of rate limiting is a code vulnerability if we are talking about an API endpoint.

Not that discussion makes any sense at all...

Also, "not securing" doesn't mean much. Security is not a boolean. They probably have some controls, but they still have a gap in the lack of rate limiting.

[–] NateNate60@lemmy.world 0 points 4 months ago (2 children)

It is a vulnerability, but exploiting that vulnerability is not generally considered by security experts to be "hacking" in the usual meaning of that term in academic settings. Using an open or exposed API, even one with a sign that says "don't abuse me", is generally not considered hacking.

[–] sudneo@lemm.ee 1 points 4 months ago (1 children)

I am a security professional. I would personally not care less to make the distinction, as both are very generic terms that are used very liberally in the industry.

So I don't see any reason not to call this hacking. This was not an intended feature. It was a gap, which has been used to perform things that the application writer did not intended (not in this form). If fits with the definition of hacking as far as I can tell. In any case, this is not an academic discussion, it is a security advisory or an article that talks about it.

[–] Freefall@lemmy.world 1 points 4 months ago

I was gonna say, we use hacking as a term for a lot of things, even is something like cracking is more accurate. It is like Clip vs Mag in firearms...when you say clip EVERYONE knows what you are talking about.

[–] 0xD@infosec.pub -1 points 4 months ago

Well from a professional here: It is.

[–] just_another_person@lemmy.world -3 points 4 months ago (1 children)
[–] NateNate60@lemmy.world 5 points 4 months ago (1 children)

Please provide a link to whatever source claims this.

I hold a computer science degree and this contradicts the definition of "hack" versus "exploit" used in academic settings.

[–] irreticent@lemmy.world 1 points 4 months ago

They probably typed it out themself then screenshotted it.