Links submitted by the Threat Radar community and AI curated for defenders.

Community Curated

AlienVault OTX General

SANS ISC Handlers Diary

SecurityWeek

Threatpost

Reddit ExploitDev

Latest exploits, shellcode, and vulnerability proofs-of-concept from Exploit-DB

Exploit-DB RSS Feed

Reddit ThreatIntel

Reddit BlueTeam

Reddit Reverse Engineering

Reddit Malware

Reddit Cybersecurity

Reddit NetSec

ThreatFox MISP Feed

CIRCL OSINT Feed

NCSC UK

JVN Japan

GCP Compute Engine Security

GCP Kubernetes Security

AWS Security Bulletins

CERT/CC

Tenable Research

Google Project Zero

Microsoft Security Blog

Cisco Talos

Zero Day Initiative

Palo Alto Unit 42

Krebs on Security

Kaspersky Security Blog

Check Point Research

GCVE Database

CVE Database V5

Real-world exploitation and exposure telemetry from the OffSeq Mirage honeypot fleet and Sonar internet scans — which CVEs attackers are actually exploiting and which are exposed in the wild, plus attacker IoCs. All IPs are masked; no raw victim or sensor identity is ever published.

OffSeq Mirage

Bleeping Computer

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)

CVE-2024-37568 is a vulnerability identified in lepture Authlib, a popular Python library used for authentication, specifically in handling JSON Web Tokens (JWT). The issue arises from an algorithm confusion flaw where, if the developer does not explicitly specify the cryptographic algorithm in the jwt.decode function, the library permits HMAC verification using any asymmetric public key. Normally, asymmetric algorithms (e.g., RSA, ECDSA) and symmetric algorithms (e.g., HMAC) require different key types and verification methods. This confusion allows an attacker to exploit the verification process by substituting keys or tokens, effectively bypassing the intended cryptographic protections. This vulnerability is similar to previously disclosed issues (CVE-2022-29217 and CVE-2024-33663) that also involved algorithm confusion attacks in JWT libraries. The CVSS v3.1 score of 7.5 reflects a high severity due to the vulnerability's network attack vector, low attack complexity, no privileges or user interaction required, and its impact on integrity. The flaw does not affect confidentiality or availability but allows attackers to forge or manipulate JWT tokens, potentially granting unauthorized access or elevated privileges within applications relying on Authlib for authentication. No known exploits have been reported in the wild yet, but the vulnerability demands prompt attention. The recommended fix is to upgrade to Authlib version 1.3.1 or later, where this issue is resolved, and to ensure that developers explicitly specify the expected algorithm in jwt.decode calls to prevent fallback to insecure verification methods.

Detailed information about CVE-2024-37568: n/a. Get real-time updates, technical details, and mitigation strategies.

CVE-2024-37568: n/a - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2024-37568: n/a

Threats Tagged 'cve-2024-37568'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'cve-2024-37568'

Lead Pen Test Professional