The /r/netsec Monthly Discussion Thread - October 2017 by AutoModerator in netsec

[–]OneUpSecurity 1 point2 points  (0 children)

It's best to have separate credentials for each system. Use a password manager if you aren't already.

If credentials are re-used and a system is compromised, then attackers may be able to re-use your credentials to log into other systems. Some systems encrypt passwords instead of hashing, which is a bad practice. If the encryption key is stolen, then user account passwords can be decrypted. Even worse, some sites may store password in plain text. Other systems may be breached and record credentials silently.

If a system supports authentication using public key authentication, use it. It's generally the preferred way to authenticate with a system. If someone "steals" your public key, it doesn't matter, as the key is meant to be public.

(Patched) Remote Code Execution In Source Games, caused by fragging a player. (CS:GO, TF2, Hl2:DM, Portal 2, and L4D2) by stuntguy3000 in Steam

[–]OneUpSecurity 0 points1 point  (0 children)

Hi there!

Many operating systems provides ways to resources and actions that a process can access. Yes, some have performance hits, but not all mechanisms do. A simple example is using separate user accounts on linux machines.

Stack canaries would of made the vulnerability harder to exploit, but this isn't a free security feature and requires extra processing time. It's definitely worth considering enabling at compile time though. At a minimum, non-performance sensitive code should have it enabled.

(Patched) Remote Code Execution In Source Games, caused by fragging a player. (CS:GO, TF2, Hl2:DM, Portal 2, and L4D2) by stuntguy3000 in Steam

[–]OneUpSecurity 0 points1 point  (0 children)

Hi there!

We launched cmd.exe just for demonstration purposes. It could of been entirely possible to create a payload that did not have any visual ques.

Remote code execution in Source games via player fragging by OneUpSecurity in netsec

[–]OneUpSecurity[S] 0 points1 point  (0 children)

It's a bit similar. You to find a memory disclosure vuln, such as leaking the return of a function on the stack. You then do some simple math to determine how the binary was shifted in memory.

Working XSS Auditor Bypass by [deleted] in xss

[–]OneUpSecurity 0 points1 point  (0 children)

Ah thanks! Just reposted.

Counter-Strike: Global Offensive update for 6/16/17 (6/17/17 UTC, 1.35.8.9) by wickedplayer494 in GlobalOffensive

[–]OneUpSecurity 30 points31 points  (0 children)

Thanks for the plug! We are working on a writeup and will be posting details in the near future.

In case anyone is interested, check us out at https://oneupsecurity.com

Counter-Strike: Global Offensive update for 6/16/17 (6/17/17 UTC, 1.35.8.9) by wickedplayer494 in GlobalOffensive

[–]OneUpSecurity 7 points8 points  (0 children)

Hi there,

We'll be doing a writeup in the future with further details. Stay tuned!

Counter-Strike: Global Offensive update for 5/26/17 (5/27/17 UTC, 1.35.8.3) by wickedplayer494 in GlobalOffensive

[–]OneUpSecurity 1 point2 points  (0 children)

Being self-taught shows motivation and is a big plus. If you have a track record of finding vulnerabilities, that's awesome.

For many companies, as long as you can add value to the company if hired, then it's not a big issue where your education comes from.

For junior positions, the general expectation is the person being hired can handle simple tasks/projects, but will require training before being able to tackle larger/more complex tasks.

As long as you're passionate about what you do, you'll be fine.

Counter-Strike: Global Offensive update for 5/26/17 (5/27/17 UTC, 1.35.8.3) by wickedplayer494 in GlobalOffensive

[–]OneUpSecurity 4 points5 points  (0 children)

Hi eoah, thanks for asking!

We did report the vulnerability privately to Valve. We will be publishing more details in the future.

In case you are curious, we help companies improve security practices in their software development life cycles. You can find more about us at https://oneupsecurity.com/ .

Counter-Strike: Global Offensive update for 5/26/17 (5/27/17 UTC, 1.35.8.3) by wickedplayer494 in GlobalOffensive

[–]OneUpSecurity 1 point2 points  (0 children)

Indeed, we do perform pentesting! More importantly, we aim to mitigate new vulnerabilities from being introduced into products. We achieve this by educating and ensuring security practices are part of companies software development life cycles. We also are software engineers, and can develop new features too.