Pretty impressive to introduce 1400 CVEs in a project that's only ~7 months old.
We eliminated 1,400 CVEs in NanoClaw's container images
11–20 of 54 posts
Re: We eliminated 1,400 CVEs in NanoClaw's container images
#12Re: We eliminated 1,400 CVEs in NanoClaw's container images
#13so s/bookworm/trixie/g didn't work then? Yes, this is mostly a joke, I am able to understand the difference between base distros.
Re: We eliminated 1,400 CVEs in NanoClaw's container images
#14Why is the Node ecosystem like this? Why do people continue to choose it for popular projects vs. anything else?
Re: We eliminated 1,400 CVEs in NanoClaw's container images
#15Pretty impressive to introduce 1400 CVEs in a project that's only ~7 months old.
These are CVEs in the base image and in standard lib dependencies. For example, just scanned an unhardened image I built today: Unhardened: docker.io/nanoco/nanoclaw:agent-alpha 71 packages, 344 unique CVEs, linux/arm64 PACKAGE VERSION TYP C H M L N TOT ----------------------------------------------------------- expat 2.5.0 deb 0 4 18 1 2 25 curl 7.88.1 deb 4 4 6 0 7 21 hono 4.12.14 npm 0 1 18 2 0 21 libtiff 4.5.0 de…
Re: We eliminated 1,400 CVEs in NanoClaw's container images
#16Earlier quoted context omitted.
These are CVEs in the base image and in standard lib dependencies. For example, just scanned an unhardened image I built today: Unhardened: docker.io/nanoco/nanoclaw:agent-alpha 71 packages, 344 unique CVEs, linux/arm64 PACKAGE VERSION TYP C H M L N TOT ----------------------------------------------------------- expat 2.5.0 deb 0 4 18 1 2 25 curl 7.88.1 deb 4 4 6 0 7 21 hono 4.12.14 npm 0 1 18 2 0 21 libtiff 4.5.0 de…
Are these real findings, or a situation in which fixes have been backported? At one place I worked, the corpsec guys were wildly incompetent and would try to bury me in "CVEs" in my systems that were nothing but "vulnerable" software versions with all of the "identified" vulnerabilities fixed by Debian backported patches.
Re: We eliminated 1,400 CVEs in NanoClaw's container images
#17I'm convinced you can tackle 5-10 "CVEs" a day, make a little dashboard, put some pretty graphs on it, and send it to your exec team and probably get accolades. Nevermind that the CVEs had nothing to do with your product.
Re: We eliminated 1,400 CVEs in NanoClaw's container images
#18Re: We eliminated 1,400 CVEs in NanoClaw's container images
#19Pretty impressive to introduce 1400 CVEs in a project that's only ~7 months old.
These are CVEs in the base image and in standard lib dependencies. For example, just scanned an unhardened image I built today: Unhardened: docker.io/nanoco/nanoclaw:agent-alpha 71 packages, 344 unique CVEs, linux/arm64 PACKAGE VERSION TYP C H M L N TOT ----------------------------------------------------------- expat 2.5.0 deb 0 4 18 1 2 25 curl 7.88.1 deb 4 4 6 0 7 21 hono 4.12.14 npm 0 1 18 2 0 21 libtiff 4.5.0 de…
Re: We eliminated 1,400 CVEs in NanoClaw's container images
#20Pretty impressive to introduce 1400 CVEs in a project that's only ~7 months old.