#cve202421412
Live, measured metrics for the hashtag #cve202421412 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cve202421412
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.online (Mastodon public tags API) · fetched 2026-08-03 17:59 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-08-03 17:59 UTCNo related tags with measured usage found for #cve202421412.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-08-03 17:59 UTCEverything below is measured over the latest 2 public posts (spanning ~3954 hours).
Posting hours (UTC)
Languages: Basque (1)
Avg boosts / post: 2
Top of the latest posts
網路捷徑檔案安全機制繞過漏洞遭到利用超過一年，攻擊者用於散布數種竊資軟體 | iThome Link📌 Summary: 微軟在今年2月例行更新中修補了網路捷徑檔案安全繞過漏洞CVE-2024-21412，但駭客卻利用這項漏洞來散布多種竊資軟體，攻擊範圍涵蓋北美、西班牙和泰國。資安業者Fortinet在分析中發現，攻擊者製作指向特定遠端伺服器的惡意URL檔案，並在受害電腦下載LNK檔案，誘使受害者執行該檔案，從而推進攻擊。研究人員看到駭客使用兩種不同程式碼注入工具來繞過防禦
Do you happen to know which binary or binaries are affected by either CVE-2024-21412 or CVE-2024-21351? I would rather not download +1GB of updates to just check that... #CVE202421412 #CVE202421351
#cve202421412 across platforms
every network with a public tag surfaceFollow #cve202421412 straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/cve202421412