Technology

58137 readers

4485 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

[email protected]

108

Nothing's iMessage solution might not be as secure as we thought (www.androidpolice.com)

submitted 10 months ago by [email protected] to c/[email protected]

28 comments fedilink hide all child comments

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

[–] [email protected] 5 points 10 months ago (1 children)

The sheer volume of cves is not necessarily an indicator for insecurity. The CVE system is pretty bad and rulings are mostly arbitrary. For example, there was a recent curl "CVE", where an overflow happened in some part of the app which was not relevant to security. I don't remember the details, but the only solution to this apperent mess was that the main contributor of curl is becoming one of the guys that evaluate CVEs.

CVE is a measure for the US government, and always assumes the worst in any case.

That being said, I agree with you.

[–] [email protected] 2 points 10 months ago* (last edited 10 months ago)

I know what curl CVE you're referring too.
Yeah, that was pretty stupid, they marked it high severity when 1 It was already patched like a year prior and 2 it was a complete non-issue in the first place.
Then some fuckin AI put forth another bogus CVE based on the one you're referring.
The curl dev was pissed, and rightfully so.

And You're right, it's more so the details of the CVEs that's important then the actual CVEs themselves.