Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
As far as I know Steam's graphics support is kinda of like it's still 2003.
"do not open non-Steam urls within Steam".
and since you cannot upload that format to Steam, this should be unproblematic ... well, besides workshop content and then it depends on the game how bad this will end.
Yup. And with vulns like these, we're just fortunate that this didn't affect a format people can use in chat windows or in community content.
I just never use the steam in-game browser at all. They don't update it as quickly as dedicated browser vendors do, it's been caught out of date with pants down before.
There was a related bug that affected Dota 2 quite dangerously. It took them over a year to patch it. That vuln actually allowed arbitrary remote code execution (full OS takeover) as I recall.
Just don't use the in-game browser for anything, that's my simple rule. They're not particularly hasty in patching it.
https://help.steampowered.com/en/faqs/view/6639-EB3C-EC79-FF60
True but not anought ...
Even a trusted web site can use an advert with an infected webp image and you do not need to click it to let the code embedded inside the malicious picture been executed on your pc.
The best solution is ; do not use the build-in browser.
Use at your own risk, and most often reason someone may use in-game browser would be to check for info such as youtube, game forums, game wiki, or etc. Also it's not idea to use any personal banking, amazon order, and such via in-game browser as they're often outdated.
Another thing to note is when there custom browser, you check what it has, if it self-contained to not allowing access to what outside of it, and if it affected by said kind of vulnerabilities, as some requires certain things to be there in order to work, hence example when google, edge, and such had to panic to update their browser multiple times in the year due to said zero day vulnerability, Steam didn't had to because it didn't affect them due to lacking the things it need enable, or missing them, or unable to execute action due to restrictions. But since it old thing it still use at your own risk.
I would say to someone don't use "embedded browser" if they're unable to think for themselves, or need supervision that meant they need someone to monitor them.
It has the same capabilitity, displaying webp picture, parsing and executing java script and it's based on a barebone old version of cef from 2020 without any security fixe apply since the day one of cef 85....
So at least we are agree on that : do not use the build-in browser.
if you want to verify what i say just open it and go to https://browserleaks.com/
i sincerely hope steam will upgrade the cef to v118+ after january...
omwb to my old steam client.
He's saying the browser is self contained in Steam unlike other browsers that don't sandbox.
This makes anything that happens in the browser stay within Steam and not spread outside of the client.
Yes it's sandboxed but it does not change the problem.. even cef have allready patched this vulnerability, so guess why ? it's sanboxed like all browser that allready patched it ....
Not every browser based on CEF is sandboxed.
Wich one ?
chrome, brave, edge are sandboxing chromium xd