-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security] EMBA report of 20240809_NanoKVM_Rev1_2_0.img #115
Comments
Hi, thank you for your feedback! |
Context is needed here. How many are exploitable from remote? How many require an authenticated user? How many affect the web UI?
This is the important part.
This is important if you don't change the default passwords.
These are pretty much irrelevant as once you have root on the device, you can do whatever the hell you like anyway. |
Thanks. On second thought, it's mostly HTML, so I just uploaded it to a repo: https://github.com/lwbt/emba_20240809_NanoKVM_Rev1_2_0.img Unfortunately it has to be downloaded before it can be viewed in a browser. |
Most can be solved by updating buildroot and because linux 5.10.y is LTS you can merge the fixes from kernel.org. It tested it with an image build my updated repository:
|
Out of curiosity I ran emba today on the latest image. Below you can find an excerpt. I removed the components which had 0 CVEs to not make the list look much longer than necessary.
Don't just look the the CVEs. Stack canaries, RELRO, PIE and others are also important.
From what I can tell the images are simply attached to a release here on GitHub, there is no automated build pipeline and workflow to build, test and verify. I understand that one has to start somewhere to get a product out of the door before improving tooling. But the product is also advertised as being superior to traditional IPMI/KVM solutions, and to be honest, this report is devastating and discloses ignorance of industry standards going back 10 years and more.
If there is something like a board support supplier involved Sipeed should also talk to them and get as many issues resolved as possible. Shipping an LTS Linux kernel from a few years ago and a few not so fresh dependencies may pass. Shipping 1188 High rated CVEs is not acceptable.
I can provide the full HTML log to everyone who is interested and doesn't want to spin up Kali Linux with EMBA for a 2-3 hours on 16 cores themselves.https://github.com/lwbt/emba_20240809_NanoKVM_Rev1_2_0.img
The text was updated successfully, but these errors were encountered: