Skip to content
Latest
Crime Stoppers Vendor Breach: Protect Confidentiality When Reporting Routes ChangeBinance Estimates $6.3 Billion Impact: Separate Frozen Funds From RecoverySignal RingRTC Hang-Up Flaw: Update the Client, Verify the Call EndsPillow Image-Processing Flaw: Patch the Worker Behind the UploadWasmtime on Arm: Check the Separate br_table Sandbox EscapeBlastmail Breach: Protect the Audience Data Behind Your NewsletterKeyDrift on Cisco SD-WAN: Patch the Entry Point, Investigate the ControllerPostiz Token Forgery: Patch the Publisher, Review Organization AccessBrotli Enters CISA KEV: Patch Node.js and Trace Every Decompression PathWasmtime Sandbox Escape: Patch the Engine Behind Your Wasm WorkloadsQuest Quanum Incident: Protect Patient Data While Keeping Orders MovingPulsar Token Bypass: Check Anonymous Fallback and Patch BrokersCisco Expressway Root RCE: Patch the Cluster and Check Service ReachabilityPulsar Manager Is Retired: Remove the Console and Recover Cluster Credentials

IOC Passport

CVE-2024-21762

CVEArticle-derived observationArchived observationReported in 3 articlesWatch this →

A CVE identifier referenced in published reporting. It is vulnerability context, not a malicious indicator or feed verdict.

This context-only value aged beyond its 90-day contextual reporting window. No applicable exact provider check exists for this type, so placement is based on reporting recency alone. Archive-cleared or archived does not mean clean, inactive, benign, remediated, resolved, or safe, and this lifecycle does not change current verified-feed admission.

Current verified-feed status

Checking live guard…

Article reporting and current malicious-feed admission are evaluated separately.

First reported
Last reported
Article count
3
Admission policy
Context only
Research lifecycle
Archived · window ended

Related indicators

Observables that appear alongside this one in the same reporting. Co-occurrence can suggest shared infrastructure, but it does not establish common ownership, campaign identity, or actor attribution.

CVE-2022-42475CVE-2023-27997135[.]237[.]122[.]202165[.]22[.]184[.]26185[.]65[.]245[.]101f65544978b8ea0e745e573b8ee9684b200[.]79[.]113[.]136201[.]144[.]122[.]58201[.]144[.]122[.]6024fcebdeecba65004fdb0923763d74fd45[.]61[.]137[.]12662[.]171[.]185[.]979c872a0d5d5a38950e8b9ac9b488be3f9cbd560f820c95d7c38342cd558cb5c6a514d1bb62d7916475946fe7c07ac0aaaa3086be652c8b20b0b29b2730d57119b3352b42432dedc4a519f011dc8b5d5ac559cc68986933200fd5d9e4388e2f58connect-microsoft[.]comCVE-2016-4437CVE-2018-13379CVE-2020-0796CVE-2020-1206CVE-2020-1472CVE-2020-1938CVE-2021-26855CVE-2021-27076CVE-2021-36260CVE-2021-4034CVE-2021-44228CVE-2022-22972CVE-2022-27925CVE-2022-40684CVE-2022-41082CVE-2023-20198CVE-2023-32315CVE-2023-46747CVE-2023-46805CVE-2024-21887CVE-2024-36401

Newsletter

The House-Of-L Brief.

Two short reads a day on markets, cyber threats, AI, and geopolitics. A "why it matters" line on every story.

Double opt-in. One-click unsubscribe on every issue. We never share your address.