Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mstdn.social/users/jschauma/statuses/114180804466741476">Jan Schaumann (jschauma@mstdn.social)'s status on Tuesday, 18-Mar-2025 18:53:19 JST</a><a href="https://mstdn.social/@jschauma" title="jschauma@mstdn.social"><img src="https://gnusocial.jp/avatar/110518-48-20230331194031.webp" width="48" height="48" alt="Jan Schaumann" style="position: absolute; left: 0; top: 0;">Jan Schaumann</a><div><a href="https://mstdn.social/@jschauma/113054005419118591" rel="in-reply-to">in reply to</a></div></section><article><p>The secret language of coders, part N of many. Today: security vendor vulnerability announcement phrases.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4751399#notice-9306700">In conversation</a><time datetime="2025-03-18T18:53:19+09:00" title="Tuesday, 18-Mar-2025 18:53:19 JST">about 18 days ago</time> <span>from <span><a href="https://mstdn.social/@jschauma/114180804466741476" rel="external" title="Sent from mstdn.social via ActivityPub">mstdn.social</a></span></span><a href="https://mstdn.social/@jschauma/114180804466741476">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/4319857">phrase -- actual meaning
"0-Day" -- a recently identified and properly disclosed vulnerability, usually with an already assigned CVE ID"sophisticated attack" -- somebody got phished"exploitation is trivial" -- ...assuming specific prerequisites, like e.g., being able to change a configuration file, guessing a 128-bit UUID, or hoping non-default settings are combined in an illogical manner"which we have named &lt;terrible pun&gt;" -- we really, really hope this name takes off even though it's a very narrowly scoped vulnerability, that would be so cool"nation state attacker" -- off-the-shelf vuln scanner traffic from China and/or a country we couldn't place without consulting a map"we have developed a tool to detect..." -- here's a shell script running "find / -type f -name ...""RCE can't be ruled out" -- we tried to achieve remote code execution, but couldn't"we're releasing this information in the hope that it will help others" -- we want to preempt somebody else publishing this information before us"OSINT" -- github dorking"we take the security and privacy of our customers seriously" -- whoops</a></label><br><a href="https://media.mstdn.social/media_attachments/files/114/180/793/442/873/233/original/104d8f63b3387800.png" rel="external">https://media.mstdn.social/media_attachments/files/114/180/793/442/873/233/original/104d8f63b3387800.png</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Jan Schaumann (jschauma@mstdn.social)'s status on Tuesday, 18-Mar-2025 18:53:19 JST Jan Schaumann
in reply to
The secret language of coders, part N of many. Today: security vendor vulnerability announcement phrases.
In conversationabout 18 days ago from mstdn.socialpermalink
Attachments
1. phrase -- actual meaning "0-Day" -- a recently identified and properly disclosed vulnerability, usually with an already assigned CVE ID "sophisticated attack" -- somebody got phished "exploitation is trivial" -- ...assuming specific prerequisites, like e.g., being able to change a configuration file, guessing a 128-bit UUID, or hoping non-default settings are combined in an illogical manner "which we have named <terrible pun>" -- we really, really hope this name takes off even though it's a very narrowly scoped vulnerability, that would be so cool "nation state attacker" -- off-the-shelf vuln scanner traffic from China and/or a country we couldn't place without consulting a map "we have developed a tool to detect..." -- here's a shell script running "find / -type f -name ..." "RCE can't be ruled out" -- we tried to achieve remote code execution, but couldn't "we're releasing this information in the hope that it will help others" -- we want to preempt somebody else publishing this information before us "OSINT" -- github dorking "we take the security and privacy of our customers seriously" -- whoops
  https://media.mstdn.social/media_attachments/files/114/180/793/442/873/233/original/104d8f63b3387800.png

Public

Embed Notice

HTML Code

Corresponding Notice