Top all-time · #10411
АО «ПМ»
Company blog · amonitoring.ru/articlesecuritysystems
АО «ПМ» is the company blog at amonitoring.ru, writing about security and systems. Since 2019, 7 different Hacker News readers have linked it 8 times, most often “One More Steam Windows Client Local Privilege Escalation 0day”. No feed was found, so read it on the site itself.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN readers link this blog's writeups on Steam privilege-escalation zero-days, including a second Steam 0-day report. Comments cite it as a source and clarify details of the researcher's Valve ban.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
«Перспективный мониторинг» занимается исследованиями состояния безопасности информационных систем (ИС) и программных продуктов, мониторингом и предотвращением атак, расследованиями инцидентов, разрабатывает решения по информационной безопасности (ИБ)
Most-linked posts?
- One More Steam Windows Client Local Privilege Escalation 0day4 people · 4 mentions · first linked 2019-08-20
- Steam Windows Client Local Privilege Escalation 0day2 people · 2 mentions · first linked 2019-08-07
What Hacker News says?
I wanted to note that the researcher was not banned at HackerOne, he was only banned from reporting bugs to Valve. This is written in the article about a second vulnerability [1] [1] https://amonitoring.ru/article/onemore_steam_eop_0day/
Comment linking /article/onemore_steam_eop_0day/
on “Researcher banned on Valve's bug bounty program publishes second Steam 0-day”Submitted Steam Windows Client Local Privilege Escalation 0day as a story · 407 points
HN discussionThis wouldn't be anywhere near as severe a problem as it is if Steam's service wasn't running as something as ridiculously privileged as NTAUTHORITY\SYSTEM. On the plus side, reading the writeup [0] it seems unlikely that this affects the Linux client (or even if it does, it's at least limited to the current user account). So I guess Steam can continue to live on my machine for another day. [0]: https://amonitoring.…
Comment linking /article/onemore_steam_eop_0day/
on “Researcher banned on Valve's bug bounty program publishes second Steam 0-day”Submitted One More Steam Windows Client Local Privilege Escalation 0day as a story · 4 points
HN discussionI just don't expect every developer to be an expert at packaging their app. There's a thousand things to think of, and they might do an unreasonable hack just to get away with distribution. If you get your packages from a single source, you mostly have to trust that source (lower attack surface), and can be assured they will meet a minimum quality level. Example oopses from valve (but really, most vendors have their…
Comment linking /article/steamclient-0day/
on “Reasons to prefer Linux over Windows (2014)”Submitted One More Steam Windows Client Local Privilege Escalation 0day as a story · 1 points
HN discussionFor another case like this, look up "steam privilege escalation" https://amonitoring.ru/article/steamclient-0day Valve tried to downplay this too. Privilege escalation is an attack vector that's easy to downplay
Comment linking /article/steamclient-0day
on “Ex-NSA hacker drops zero-day for Zoom”Not necessarily. [0] Also, it is actually quite trivial bypassing UAC prompt in Windows. It simply gives a false sense of security. Something as simple as SilentCleanup [1] still works to this day. This will bypass UAC with little effort. Even worse, following that, it is also trivial to get NT AUTHORITY\SYSTEM using Windows Management Instrumentation Event Subscription. [2] I've done it as an exercise in Go out of…
Comment linking /article/steam_vuln_3/
on “Steam for Linux client adds support for Linux namespaces”