Event JSON
{
"id": "6d7ff02c211fc0b89ad16a8ce299898ff8a417a9e9f871267831347e781dad45",
"pubkey": "41c7b8361f0e33bb91930334aade1854b6f5a4435767bd7aa21da1013a3d5b05",
"created_at": 1695829511,
"kind": 1,
"tags": [
[
"p",
"74d972ae87ff9199eb1e4aec71152d6c71d05eb26fa09aedbba04eca7c4ffc93",
"wss://relay.mostr.pub"
],
[
"p",
"979a28fa43702f9be4e468836a5b120cc4265237f4295fcb4a9b28e2a71d1c6b",
"wss://relay.mostr.pub"
],
[
"e",
"887da05b8aed42a3d1471071d88b68d09e859e455cb60019117e0feec0794406",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.town/notes/9k5hf39aaiwjehhj",
"activitypub"
]
],
"content": "nostr:npub1wnvh9t58l7gen6c7ftk8z9fdd3caqh4jd7sf4mdm5p8v5lz0ljfsej899h It appears that Microsoft has patched CVE-2023-4863 which was the original CVE Google reported 2 weeks ago. I'm guessing this means it should also resolve CVE-2023-5129 if I'm not mistaken.\n\nAccording to the release notes, 117.0.2045.31 should resolve this...",
"sig": "e36d2a82fc0b6707cd86ec530dff877d1dea4a35aa9ce5fd939368d4f90c94aab08729bba592a1907f40749ba4c48ab6865a789b83fd7dfc5f2064183d6aa4ae"
}
