Linux

48143 readers

1318 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Discussion of CVE-2017-5226 (lemmy.zip)

submitted 4 months ago* (last edited 4 months ago) by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

CVE-2017-5226 is a issue with bubblewrap that allows a program running in a sandbox to excape and get the same privileges as a the parent process. I recently discovered this by mistake and it is fairly concerning to me. ~~I believe it applies to Flatpak as Flatpak uses bubblewrap under the hood.~~

~~Many people like to boast about how secure and private flatpak and some even run untrusted software in it. However, the reality is that there hasn't been a lot of testing and the fact that this CVE still exists but isn't well known is concerning.~~

The reason it wasn't patched is that it is really hard to properly fix. The work around is to call bubblewrap with the --new-session flag as this effectively prevents the excape. However, this breaks interactive programs such as htop. Also the bubblewrap team believes this is a issue that should be solved downstream as this CVE is technically not a CVE in the traditional sense.

I think it is still better to run flatpak over non flatpak but it is something to be aware of

Edit:

It doesn't apply to flatpak as it is patched in 1.3.1and higher https://github.com/flatpak/flatpak/security/advisories/GHSA-7gfv-rvfx-h87x

Basically this is a communication and people problem not a technical one

Edit2:

This isn't exploitable on modern systems with 6.1 or newer with the way most distros compile the kernel

you are viewing a single comment's thread
view the rest of the comments

[–] Bero 4 points 4 months ago (1 children)

Well the exploit in the CVE needs the kernel function.
And it's disabled as default since 6.2.

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 children)

my ubuntu 22 AWS VM only got 6.2 in september, and I haven't rebooted yet so it's still on 5.15. probably tons of desktops and servers are still using < 6.2

[–] [email protected] 3 points 4 months ago (2 children)

Which is why they said "modern" kernels. LTS systems are usually not going for modern. :)

[–] [email protected] 4 points 4 months ago (1 children)

we can disagree on the definition of modern.

[–] [email protected] 1 points 4 months ago

That's true. It varies from person to person. I, for example, am an Arch user, so modern for me is only around a year or so. Ubuntu 22.04 is old in my eyes, mostly because a newer LTS was released after it.

You might define Ubuntu 22.04 as new, because it's still fully supported.

It's just a question of how you define modern/recent.

[–] [email protected] 3 points 4 months ago

Well, “modern” is a relative term, so that might not have been a good pick...