Threat actors can exploit a security vulnerability in the Rust standard library to target Windows systems in command injection attacks.
  • 5C5C5CEnglish
    60·
    9 months ago

    Funny how the headline makes it sound like a Rust specific problem, as if the Rust language is unsafe or the core team was incompetent, but then other affected language standard libraries include

    • Erlang (documentation update)
    • Go (documentation update)
    • Haskell (patch available)
    • Java (won’t fix)
    • Node.js (patch will be available)
    • PHP (patch will be available)
    • Python (documentation update)
    • Ruby (documentation update)

    So actually this is a vulnerability that originates in Windows, and Rust and Haskell are the only languages that are actually protecting users from it as of right now, with Node.js and PHP to follow.

    • sepulcher@lemmy.caEnglish
      73·
      9 months ago

      I’m honestly surprised windows can even exist at this point.

      It’s mind-boggling to me that people would dedicate their lives to learning that system when it’s such a shoddy piece of crap.

      It’s amazing what a motivator money can be.

    • Blue_Morpho@lemmy.worldEnglish
      131·
      9 months ago

      It’s not Rust, the language or even Windows.

      It’s if you write a program that allows the end user to call a command prompt and don’t carefully sanitize the input, bad things could happen.

      I mean, maybe Windows could do something different but if you wrote JavaScript that takes text input from a webpage and pass it to “sudo bash ##commands”, you’re going to have a bad time.

      It’s complete click bait because Rust has a reputation for security.

      • wkk@lemmy.worldEnglish
        9·
        9 months ago

        It’s definitely not Rust’s fault, but it’s kinda Windows’ one and cmd.exe escape logic… It’s really difficult to write logic that will correctly escape any argument given to it, cmd.exe really is a pain to deal with :/

        The Rust security team faced a significant challenge when dealing with cmd.exe’s complexity since they couldn’t find a solution that would correctly escape arguments in all cases.

        As a result, they had to improve the robustness of the escaping code and modify the Command API. If the Command API cannot safely escape an argument while spawning the process, it returns an InvalidInput error.

        “If you implement the escaping yourself or only handle trusted inputs, on Windows you can also use the CommandExt::raw_arg method to bypass the standard library’s escaping logic,” the Rust Security Response WG added.

        I get that in situations where they can’t safely escape a parameter they’ll just stop with an error, which sound as sane as one could go with this!

        • Blue_Morpho@lemmy.worldEnglish
          1·
          9 months ago

          It’s really difficult to write logic that will correctly escape any argument given to it, cmd.exe really is a pain to deal with :/

          Is cmd.exe even a thing in Windows? I know it exists and you can run it but I thought I read that the default is Power Shell now. (Just Googled, yeah Powershell replaced cmd.exe by default in 2022.)

          • wkk@lemmy.worldEnglish
            1·
            9 months ago

            https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createprocessa

            To run a batch file, you must start the command interpreter; set lpApplicationName to cmd.exe and set lpCommandLine to the following arguments: /c plus the name of the batch file.

            Because a batch file (.bat or .cmd) is basically a set of cmd.exe instructions I guess that’s why you can’t get away from it.

            And as if making sense of this CreateProcessA system call wasn’t funny enough, you also need to figure out how to safely prepare that lpCommandLine for it following all of cmd.exe’s weird escaping rules… lol

              • wkk@lemmy.worldEnglish
                2·
                9 months ago

                If you can avoid running batch files altogether then great, amazing. But there are projects out there using Rust that still depend on running those and that’s the focus of the issue… But yeah I cannot wait until the day I won’t hear about cmd.exe again.

  • ShittyBeatlesFCPres@lemmy.worldEnglish
    5·
    9 months ago

    I’m no Windows expert but I wonder why they don’t offer a “Windows Now” type product that breaks backwards compatibility but is more secure. Something that doesn’t even come with cmd.exe because Powershell exists. (Not that it would solve the issue in the article. This is more an aside.) Windows RT was probably not that. From what I understand, it was a “Windows But Weirdly Limited” product. I mean full Windows that can run reasonably modern software but does away with all the backwards compatibility stuff only certain businesses need.

    Apple is ruthless about that and it doesn’t seem to hurt them. Linux distros barely bother because you can always find a way to run an old version if you really want to. It’s kind of neat that Windows can still run Excel 1.0 or whatever but as a non-Windows user, it seems like they could break with the past and fix a lot of security issues for a fraction of what they’re spending on A.I. PowerPoints or whatever.

    • pycorax@lemmy.worldEnglish
      6·
      9 months ago

      That was what 10X was supposed to be. It was supposed to be practically a full rewrite of the OS to shake off all the legacy cruft with support for existing Win32 apps through containerization. It was dropped along with the Surface Neo and they shifted their focus to Win 11 instead which is a real shame.

      • Thomas@discuss.tchncs.deEnglish
        1·
        9 months ago

        Yes, one of the factors that contributed to the demise of Windows Mobile was the lack of backwards-compatibility for apps between 7, 8, an 10.