3 ms·

> I don't see what the big deal is. Let's say that a Windows user wants to use sandboxie to isolate web components when browsing, until Aug of this year. You'

by IncRnd 9y ago

> I don't see what the big deal is. Let's say that a Windows user wants to use sandboxie to isolate web components when browsing, until Aug of this year. You're Pwned: https://nvd.nist.gov/vuln/detail/CVE-2017-12480 https://nvd.nist.gov/vuln/detail/CVE-2017-12480

AnIdiotOnTheNet 9y ago
I think I'm missing something. It has been a while since I've used Sandboxie, but it seems like this is a behavioral oversight on it's part.
- IncRnd 9y ago
  > It has been a while since I've used Sandboxie, but it seems like this is a behavioral oversight on it's part. What do you mean by a behavioral oversight? The installer loaded a non-existent dll from the temp folder. Any DLL of the same name would get executed upon installation of Sandboxie. That's why DLL hijacking is an issue.
  - AnIdiotOnTheNet 9y ago
    The link you gave gives a single line description of the issue. It isn't very helpful in understanding what conditions were required to exploit. Is this a Sandboxie installer issue or all installers? If the latter, yeah that's a problem, but there are a lot of ways to fix it that don't involve crippling the flexibility. Edit: ok, read the medium link at the bottom. This is an issue with Sandboxie's installer behavior, for which I think it is unfair to blame the way Windows searches for and loads DLLs.
    - IncRnd 9y ago
      > The link you gave gives a single line description of the issue. It isn't very helpful in understanding what conditions were required to exploit. Is this a Sandboxie installer issue or all installers? The single line description is literally an answer to both of those questions, "Sandboxie installer 5071703 has a DLL Hijacking or Unsafe DLL Loading Vulnerability via a Trojan horse dwmapi.dll or profapi.dll file in an AppData\Local\Temp directory." > Edit: ok, read the medium link at the bottom. This is an issue with Sandboxie's installer behavior, for which I think it is unfair to blame the way Windows searches for and loads DLLs. The vulnerability is literally caused by the dll load path containing the cwd. That is the subject of this entire thread.
      - AnIdiotOnTheNet 9y ago
        If that were true, it'd be applicable to every installer on earth. Sandboxie installer does something it shouldn't. But hey, fuck it, let's throw the baby out with the bathwater and have namespace conflicts because now all DLLs must be in system32 or some bullshit. For that matter, let's just not use computers at all! That's where vulnerabilities come from after all.
        IncRnd 9y ago
        None of that has anything to do with the discussion about binary planting, one variant of which is dll planting due to the cwd directory being used as a path component in microsoft windows versions.

by IncRnd 9y ago

AnIdiotOnTheNet 9y ago

I think I'm missing something. It has been a while since I've used Sandboxie, but it seems like this is a behavioral oversight on it's part.

IncRnd 9y ago
> It has been a while since I've used Sandboxie, but it seems like this is a behavioral oversight on it's part. What do you mean by a behavioral oversight? The installer loaded a non-existent dll from the temp folder. Any DLL of the same name would get executed upon installation of Sandboxie. That's why DLL hijacking is an issue.
- AnIdiotOnTheNet 9y ago
  The link you gave gives a single line description of the issue. It isn't very helpful in understanding what conditions were required to exploit. Is this a Sandboxie installer issue or all installers? If the latter, yeah that's a problem, but there are a lot of ways to fix it that don't involve crippling the flexibility. Edit: ok, read the medium link at the bottom. This is an issue with Sandboxie's installer behavior, for which I think it is unfair to blame the way Windows searches for and loads DLLs.
  - IncRnd 9y ago
    > The link you gave gives a single line description of the issue. It isn't very helpful in understanding what conditions were required to exploit. Is this a Sandboxie installer issue or all installers? The single line description is literally an answer to both of those questions, "Sandboxie installer 5071703 has a DLL Hijacking or Unsafe DLL Loading Vulnerability via a Trojan horse dwmapi.dll or profapi.dll file in an AppData\Local\Temp directory." > Edit: ok, read the medium link at the bottom. This is an issue with Sandboxie's installer behavior, for which I think it is unfair to blame the way Windows searches for and loads DLLs. The vulnerability is literally caused by the dll load path containing the cwd. That is the subject of this entire thread.
    - AnIdiotOnTheNet 9y ago
      If that were true, it'd be applicable to every installer on earth. Sandboxie installer does something it shouldn't. But hey, fuck it, let's throw the baby out with the bathwater and have namespace conflicts because now all DLLs must be in system32 or some bullshit. For that matter, let's just not use computers at all! That's where vulnerabilities come from after all.
      - IncRnd 9y ago
        None of that has anything to do with the discussion about binary planting, one variant of which is dll planting due to the cwd directory being used as a path component in microsoft windows versions.