Weak Default Configuration for uksp and ukswrand
#455
Unanswered
lrapp-x41-pub
asked this question in
General
Replies: 1 comment
-
|
@lrapp-x41-pub, since we are already (viciously) using the Unikraft Discord server for discussions, meetings, brainstorming and jokes (mostly bad, we do what we can), we will close the Discussions tab. We will do this on Friday, March 31, 2023. Please move any discussions or questions on the Unikraft Discord server. See you all there! 🤝 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
From a security perspective, the default configuration for
ukspandukswrandis not the most secure one.uksp:STACKPROTECTOR_REGULARinstead ofSTACKPROTECTOR_ALLLIBUKSP_VALUE_USECONSTANTinstead ofLIBUKSP_VALUE_RANDOMukswrand:LIBUKSWRAND_INITIALSEED_TIMEinstead ofLIBUKSWRAND_INITIALSEED_RDRANDThe default configuration leads to known or predictable canary values.
An attacker might be able to use this knowledge to embed the known canary value at the correct place in the exploit string and overwrite the canary with the correct value to circumvent stack smashing protection that way.
As many users might use the default configuration, it should be considered to choose the most secure option as default configuration.
Beta Was this translation helpful? Give feedback.
All reactions