Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. #LPE — Local Privilege Escalation.

#LPE — Local Privilege Escalation.

Scheduled Pinned Locked Moved Uncategorized
lpercecopyfaildirtyfrag
10 Posts 5 Posters 1 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • jwildeboer@social.wildeboer.netJ This user is from outside of this forum
    jwildeboer@social.wildeboer.netJ This user is from outside of this forum
    jwildeboer@social.wildeboer.net
    wrote last edited by
    #1

    #LPE — Local Privilege Escalation. A class of vulnerabilities that need a local user account on the target machine to reach higher levels of privilege, up to superuser/root

    #RCE — Remote Code Execution. A class of vulnerabilities that can be exploited over unprivileged network connections, giving the attacker privileged access to the target machine.

    #CopyFail, #DirtyFrag are LPEs that affect Linux systems. LPEs are typically harder to exploit than RCEs.

    Hope this helps to avoid Clickbait.

    agowa338@chaos.socialA jfkimmes@social.tinycyber.spaceJ bortzmeyer@mastodon.gougere.frB 3 Replies Last reply
    1
    0
    • jwildeboer@social.wildeboer.netJ jwildeboer@social.wildeboer.net

      #LPE — Local Privilege Escalation. A class of vulnerabilities that need a local user account on the target machine to reach higher levels of privilege, up to superuser/root

      #RCE — Remote Code Execution. A class of vulnerabilities that can be exploited over unprivileged network connections, giving the attacker privileged access to the target machine.

      #CopyFail, #DirtyFrag are LPEs that affect Linux systems. LPEs are typically harder to exploit than RCEs.

      Hope this helps to avoid Clickbait.

      agowa338@chaos.socialA This user is from outside of this forum
      agowa338@chaos.socialA This user is from outside of this forum
      agowa338@chaos.social
      wrote last edited by
      #2

      @jwildeboer

      Do we actually know that CopyFail cannot be exploited remotely for sure though? Isn't it accessible through IPSec or something?

      silhouette@dumbfuckingweb.siteS 1 Reply Last reply
      0
      • agowa338@chaos.socialA agowa338@chaos.social

        @jwildeboer

        Do we actually know that CopyFail cannot be exploited remotely for sure though? Isn't it accessible through IPSec or something?

        silhouette@dumbfuckingweb.siteS This user is from outside of this forum
        silhouette@dumbfuckingweb.siteS This user is from outside of this forum
        silhouette@dumbfuckingweb.site
        wrote last edited by
        #3

        @agowa338 @jwildeboer dirtyfrag uses the ESP (encapsulating security payload) module that is part of IPSec. Still only exploitable locally.

        Ofc, exploits can be chained (reverse shell would be an example of getting lesser privilege user rights) but the original post is still correct.

        agowa338@chaos.socialA 1 Reply Last reply
        0
        • silhouette@dumbfuckingweb.siteS silhouette@dumbfuckingweb.site

          @agowa338 @jwildeboer dirtyfrag uses the ESP (encapsulating security payload) module that is part of IPSec. Still only exploitable locally.

          Ofc, exploits can be chained (reverse shell would be an example of getting lesser privilege user rights) but the original post is still correct.

          agowa338@chaos.socialA This user is from outside of this forum
          agowa338@chaos.socialA This user is from outside of this forum
          agowa338@chaos.social
          wrote last edited by
          #4

          @silhouette @jwildeboer

          I was talking about CopyFail, the first one, wasn't the kernel module that had that bug mainly used for handling the encryption in older IPSec implementations?

          1 Reply Last reply
          0
          • jwildeboer@social.wildeboer.netJ jwildeboer@social.wildeboer.net

            #LPE — Local Privilege Escalation. A class of vulnerabilities that need a local user account on the target machine to reach higher levels of privilege, up to superuser/root

            #RCE — Remote Code Execution. A class of vulnerabilities that can be exploited over unprivileged network connections, giving the attacker privileged access to the target machine.

            #CopyFail, #DirtyFrag are LPEs that affect Linux systems. LPEs are typically harder to exploit than RCEs.

            Hope this helps to avoid Clickbait.

            jfkimmes@social.tinycyber.spaceJ This user is from outside of this forum
            jfkimmes@social.tinycyber.spaceJ This user is from outside of this forum
            jfkimmes@social.tinycyber.space
            wrote last edited by
            #5

            @jwildeboer Good distinction to be aware of. Just to clarify, both can apply:

            #RCE must not be privileged. It gives *any* kind of remote capability to run code. Could e.g. be with the highly restricted privileges of the web server process.

            An #LPE vulnerability like #CopyFail or #DirtyFrag could however be chained with such an RCE vulnerability to get full root access to the target.

            jwildeboer@social.wildeboer.netJ 1 Reply Last reply
            0
            • jfkimmes@social.tinycyber.spaceJ jfkimmes@social.tinycyber.space

              @jwildeboer Good distinction to be aware of. Just to clarify, both can apply:

              #RCE must not be privileged. It gives *any* kind of remote capability to run code. Could e.g. be with the highly restricted privileges of the web server process.

              An #LPE vulnerability like #CopyFail or #DirtyFrag could however be chained with such an RCE vulnerability to get full root access to the target.

              jwildeboer@social.wildeboer.netJ This user is from outside of this forum
              jwildeboer@social.wildeboer.netJ This user is from outside of this forum
              jwildeboer@social.wildeboer.net
              wrote last edited by
              #6

              @jfkimmes Feel free to read as "a level of access that goes beyond what was intended" or something similar. My point is that many out there fail to mention the current wave is LPE, not RCE and that LPEs have a different risk assessment than RCEs.

              jfkimmes@social.tinycyber.spaceJ 1 Reply Last reply
              0
              • jwildeboer@social.wildeboer.netJ jwildeboer@social.wildeboer.net

                @jfkimmes Feel free to read as "a level of access that goes beyond what was intended" or something similar. My point is that many out there fail to mention the current wave is LPE, not RCE and that LPEs have a different risk assessment than RCEs.

                jfkimmes@social.tinycyber.spaceJ This user is from outside of this forum
                jfkimmes@social.tinycyber.spaceJ This user is from outside of this forum
                jfkimmes@social.tinycyber.space
                wrote last edited by
                #7

                @jwildeboer Totally, I appreciate your post and meant this as more of a clarification that it's not black and white, and both can apply.

                1 Reply Last reply
                0
                • jwildeboer@social.wildeboer.netJ jwildeboer@social.wildeboer.net

                  #LPE — Local Privilege Escalation. A class of vulnerabilities that need a local user account on the target machine to reach higher levels of privilege, up to superuser/root

                  #RCE — Remote Code Execution. A class of vulnerabilities that can be exploited over unprivileged network connections, giving the attacker privileged access to the target machine.

                  #CopyFail, #DirtyFrag are LPEs that affect Linux systems. LPEs are typically harder to exploit than RCEs.

                  Hope this helps to avoid Clickbait.

                  bortzmeyer@mastodon.gougere.frB This user is from outside of this forum
                  bortzmeyer@mastodon.gougere.frB This user is from outside of this forum
                  bortzmeyer@mastodon.gougere.fr
                  wrote last edited by
                  #8

                  @jwildeboer But when you write "need a local user account", many people tend to read that it means "a regular account with a shell". Actually, it can be any daemon process, even unprivileged, with a command injection (see the recent Apache RCE…).

                  jwildeboer@social.wildeboer.netJ 1 Reply Last reply
                  0
                  • bortzmeyer@mastodon.gougere.frB bortzmeyer@mastodon.gougere.fr

                    @jwildeboer But when you write "need a local user account", many people tend to read that it means "a regular account with a shell". Actually, it can be any daemon process, even unprivileged, with a command injection (see the recent Apache RCE…).

                    jwildeboer@social.wildeboer.netJ This user is from outside of this forum
                    jwildeboer@social.wildeboer.netJ This user is from outside of this forum
                    jwildeboer@social.wildeboer.net
                    wrote last edited by
                    #9

                    @bortzmeyer Yes, ultimately an RCE is also an LPE because typically you exploit a networked service that runs as a user process. But let's keep things accessible. When more people understand that from a risk assessment RCE >> LPE, that's already a bit of progress.

                    bortzmeyer@mastodon.gougere.frB 1 Reply Last reply
                    0
                    • jwildeboer@social.wildeboer.netJ jwildeboer@social.wildeboer.net

                      @bortzmeyer Yes, ultimately an RCE is also an LPE because typically you exploit a networked service that runs as a user process. But let's keep things accessible. When more people understand that from a risk assessment RCE >> LPE, that's already a bit of progress.

                      bortzmeyer@mastodon.gougere.frB This user is from outside of this forum
                      bortzmeyer@mastodon.gougere.frB This user is from outside of this forum
                      bortzmeyer@mastodon.gougere.fr
                      wrote last edited by
                      #10

                      @jwildeboer CVE-2026-23918 against Apache HTTPD was / is at the same time than CopyFail / DirtyFrag and could have been a good way to execute the POC.

                      1 Reply Last reply
                      0
                      • R relay@relay.publicsquare.global shared this topic
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • World
                      • Users
                      • Groups