search

metasepi / postmortem

Postmortem for open-source operating systems
MIT License
1 stars 0 forks source link

Choose security issues to be avoided #12

Closed master-q closed 4 years ago

master-q commented 4 years ago

It's caused by uninitialized value. ATS may easily avoid this issue with at-view. But it may be difficult at VeriFast.

Fork https://github.com/metasepi/postmortem/issues/14.

master-q commented 4 years ago

It's caused by unprivileged access. Such privilege may be easily avoided by ATS and VeriFast.

Fork https://github.com/metasepi/postmortem/issues/15.

master-q commented 4 years ago

It's also caused by unprivileged access. Such privilege may be easily avoided by ATS and VeriFast.

Fork https://github.com/metasepi/postmortem/issues/16.

master-q commented 4 years ago

It causes use-after-free on sctp_sharedkey_t value in struct sctp_keyhead list. ATS and VeriFast may avoid this.

Fork https://github.com/metasepi/postmortem/issues/17.

master-q commented 4 years ago

It's caused by no checking for length of mbuf. It may be hard to be avoided.

Fork https://github.com/metasepi/postmortem/issues/18.

master-q commented 4 years ago

It's caused by miss checking size of packets. It may be hard to be avoided.

Fork https://github.com/metasepi/postmortem/issues/19.

master-q commented 4 years ago

It's caused by IPsec specification. It may be hard to be avoided.

Fork https://github.com/metasepi/postmortem/issues/20.

master-q commented 4 years ago

All issue are forked. This issue can be closed.