Event JSON
{
"id": "f63b09342c9b29083e773346c07b964a6a893ed32e2870c7e8e3b9496bb083de",
"pubkey": "6669673770cc05daca3cdbec2127d474e8179c7c95ccf709e378057e40d41c4a",
"created_at": 1727441727,
"kind": 1,
"tags": [
[
"proxy",
"https://chaos.social/@foosel/113209621026001261",
"web"
],
[
"proxy",
"https://chaos.social/users/foosel/statuses/113209621026001261",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://chaos.social/users/foosel/statuses/113209621026001261",
"pink.momostr"
],
[
"-"
]
],
"content": "And once more a security issue with a blown up CVSS score attached. Not only that, but then also a \"oh, but I didn't know how CVSS works\". \n\nWell, thankfully how CVSS scoring works is not a secret, and I can only recommend investing the time to read through the (actually not that long) spec \u0026 guide to anyone involved in security issue reporting, esp. reporters \u0026 maintainers. \n\nCVSS3.1 spec: https://www.first.org/cvss/v3.1/specification-document\nGuide: https://www.first.org/cvss/v3.1/user-guide\n\n(yes, CVSS4 is out, but AFAIK not yet widely used)",
"sig": "82d2139e0b6146bf5e90cae0c044b0e0068d4cb76b98592e041d350e6383ab7716ad836c89b889e61f0b3483eef0e758cf6d8aa361eb6d173754d91b9c00a1e8"
}