Event JSON
{
"id": "c8ab3aec3ccd4b35987ba7cdbf3328a3ed795420174c6c0316a2945476886d3d",
"pubkey": "06eab22dbb1f669b7c8ec534a0f9011c3cf56c56c57900334b3cbb16c6afcb03",
"created_at": 1787765581,
"kind": 1,
"tags": [
[
"proxy",
"https://infosec.exchange/@ifin/117163005165042150",
"web"
],
[
"t",
"log4j"
],
[
"t",
"ifin"
],
[
"t",
"threatintel"
],
[
"proxy",
"https://infosec.exchange/ap/users/115741367687413652/statuses/117163005165042150",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/ap/users/115741367687413652/statuses/117163005165042150",
"pink.momostr"
],
[
"-"
]
],
"content": "We have some breaking news. A potential RCE in Apache #Log4J 2 (yes, really) appears to have proofs-of-concept. We have the details, the initial bug report, and mitigation recommendations. We are verifying the PoCs currently.\n\nThe putative vulnerability is in a non-standard configuration, so the blast radius is mitigated.\n\nhttps://discourse.ifin.network/t/log4j2-allowlist-bypass-could-allow-for-rce/788\n\n#ThreatIntel #ThreatIntel #IFIN",
"sig": "d10dfa9167050b5bf40541cc17659f8135bd10e103b11275964480b5ad7d39cf02741b53338799b6ab8640ed7babd3ecbcdfd2de002e4ce8995e23e3f26d12e3"
}