Skip to content

When a manufacturer correct a vulnerability in a version of software, does he have to withdraw the old vulnerable version from the market? #207

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

Open
Viko-legal opened this issue Apr 11, 2025 · 1 comment

Comments

@Viko-legal
Copy link

CRA states in article 13 (21) that : "From the placing on the market and for the support period, manufacturers who know or have reason to believe that the product with digital elements or the processes put in place by the manufacturer are not in conformity with the essential cybersecurity requirements set out in Annex I shall immediately take the corrective measures necessary to bring that product with digital elements or the manufacturer’s processes into conformity, or to withdraw or recall the product, as appropriate"

At the end of the article the "or" would mean that if the manufacturer provided corrective measure to a given vulnerability, he would not be mandatory to withdraw the old vulnerable versions of the software from the market. Is my understanding correct?

There are some case where the withdrawal could cause issues to existing project.

@bukka
Copy link
Contributor

bukka commented Apr 14, 2025

I don't think the version needs to be ever withdrawn. It's the product that should be withdrawn if the vulnerability is not fixed. Once there is a new version, the old one gets obsolote but it's not withdrawn. That's also how it usually works in software development. Old versions are not removed after security fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants