Even if this is just RCE in the script somehow (I doubt it, it can probably do anything the user running it can), it's horrifying. It means the certificate authority could just take your newly generated certificates and upload them anywhere they want. That's a catastrophic compromise in the TLS security model.
Acme.sh runs arbitrary commands from a remote server
21–30 of 71 posts
Re: Acme.sh runs arbitrary commands from a remote server
#22Earlier quoted context omitted.
> So the person claiming to be the founder of "QuantumCA" does not possess the private key corresponding to https://crt.sh/?caid=200960 - can we be sure the private key is only accessible by ssl.com's CA system? So the certificates listed here aren't issued by this person, but by the ssl.com's system? https://crt.sh/?Identity=%25&iCAID=200960&exclude=expired&de ... Correct. You can see the Quantum intermediates liste…
I find it troubling that a root CA (ssl.com) is apparently OK with lending their name in a business relationship with an actor that is actively exploiting an acme.sh 0day.
Re: Acme.sh runs arbitrary commands from a remote server
#23Even if this is just RCE in the script somehow (I doubt it, it can probably do anything the user running it can), it's horrifying. It means the certificate authority could just take your newly generated certificates and upload them anywhere they want. That's a catastrophic compromise in the TLS security model.
If the CA is compromised, can’t they just bypass ACME verification and generate a cert for your domain anyway?
If the CA can access your private key, then it can reuse (or worse, redistribute) it without anyone knowing.
Re: Acme.sh runs arbitrary commands from a remote server
#24Even if this is just RCE in the script somehow (I doubt it, it can probably do anything the user running it can), it's horrifying. It means the certificate authority could just take your newly generated certificates and upload them anywhere they want. That's a catastrophic compromise in the TLS security model.
If the CA is compromised, can’t they just bypass ACME verification and generate a cert for your domain anyway?
Re: Acme.sh runs arbitrary commands from a remote server
#25Even if this is just RCE in the script somehow (I doubt it, it can probably do anything the user running it can), it's horrifying. It means the certificate authority could just take your newly generated certificates and upload them anywhere they want. That's a catastrophic compromise in the TLS security model.
If the CA is compromised, can’t they just bypass ACME verification and generate a cert for your domain anyway?
Re: Acme.sh runs arbitrary commands from a remote server
#26I think the title buries the most horrifying part of this. The HiCA certificate authority is relying on an RCE to do an end-run around the semantics of the ACME HTTP-01 validation method. Fucked up and they should be booted from every root program for this.
They were also suggesting that user's ran the utility as root...
All really shady...
Re: Acme.sh runs arbitrary commands from a remote server
#27Was it even run through shellcheck?!
Stop writing this stuff in shell people. 95% of the time I review any (posix, nushell lacks most of these issues) shell scripts, it's obvious they would fall apart the second any string unexpectedly had a space in it. Even scripts written by darling companies of HN.
Re: Acme.sh runs arbitrary commands from a remote server
#28[0] https://www.geoffchappell.com/notes/security/aim/index.htm
Re: Acme.sh runs arbitrary commands from a remote server
#29I do wonder if what HiCA did gave possibilities to post the private key somewhere else?