201
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Aug 2024
201 points (98.6% liked)
Technology
58833 readers
6367 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
Yeah, that tells us we just don't know if this was a problem after all. Evans's statement basically claims it wasn't a vulnerability. If that's correct, then the worst thing might be if someone's browser tripped on the validation JS and allowed them down a blind alley execution path. If the claim is correct and if the page's JS never shits the bed, then in that case the only negative outcome would be someone dicking with the in-browser source could lead themselves down the blind alley, in which case who cares. The only terrible outcome seems like it would be if the claim is incorrect--i.e. if an incomplete application submission would be processed, thus allowing exploit.
Short of an internal audit, there's no smoking gun here.
It's still grossly negligent from a security perspective.