this post was submitted on 05 Jul 2024
736 points (99.2% liked)
Technology
59599 readers
3107 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- 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
view the rest of the comments
I'm not talking out of my arse here either. I don't work in security specifically but I've got a CS degree as well and it contradicts my understanding of how those terms are generally used. This is an open API endpoint, equivalent to leaving the garage door open.
But the distinction is usually unimportant. A security hole is a security hole regardless of what you call it.
To build on you analogy: if you left your garage door open and people came in and started taking your things, is that not stealing?
Of course it's stealing. But they didn't break in.
Hacking = breaking in
Data breach = stealing stuff
What about this scenario:
Would this be considered breaking in? Probably. Here is where the analogy breaks down; if I were to leave the front door of my house unlocked, even if there's a welcome mat outside, anyone who enters without my knowledge or consent can be charged with breaking and entering (yes, even though no actual breaking is involved).
The interesting thing with public APIs is that there are generally terms and conditions associated with creating an account and acquiring a key, though if you are hitting an unauthenticated endpoint you technically never agreed to them. In this particular case with Authy, it would probably be argued that the intent was to acquire data by exploiting a vulnerability in the custodian's system and use it for nefarious purposes or profit. I'd call it a hack.
The scenario you described would not be breaking in.
Terms and conditions being agreed to are not relevant for this purpose. An exposed API is one that is welcome to be exploited. If you're not requiring an API key, you're essentially saying "This API is free for anyone to use" for security purposes, regardless of what you say in the terms and conditions.