Technology

59086 readers

3245 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

114

Critical Rust flaw enables Windows command injection attacks (www.bleepingcomputer.com)

submitted 6 months ago by Rustmilian@lemmy.world to c/technology@lemmy.world

18 comments fedilink hide all child comments

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

[–] chalk46@fedia.io 16 points 6 months ago (1 children)

"not so safe now are you Rust" ~C, probably

[–] Blue_Morpho@lemmy.world 12 points 6 months ago* (last edited 6 months ago) (1 children)

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.world 9 points 6 months ago* (last edited 6 months ago) (1 children)

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.world 1 points 6 months ago (1 children)

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.world 1 points 6 months ago* (last edited 6 months ago) (1 children)

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

[–] Blue_Morpho@lemmy.world 2 points 6 months ago (1 children)

Do you have to run a batch file? Why not a Powershell script since that's the default?

[–] wkk@lemmy.world 2 points 6 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.