You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a transitive dependency on the Protobuf crate, which is currently affected by RUSTSEC-2024-0437
It is not likely that the upstreams (prometheus, opentelemetry-prometheus) will update the dependency in the next little while (as they are not directly vulnerable), but I would not want to "perma-ignore" the issue. As it is currently used by the upstream dependencies it seems to be harmless, but I wouldn't want it to be pulled in accidentally by some new code or dependency.
Describe the solution you'd like
I would like the ability to ignore the issue until the upstreams have had a chance to repair.
It would be nice if I could either
ignore it when pulled in transitively by a specific dependency.
I would like to be able to add something like (the actual vulnerable crate is protobuf, but I only want to allow the prometheus and opentelemetry-prometheus to use the vulnerable version)
ignore = [
{ id = "RUSTSEC-2024-0437", reason = "...(explanation)...", from = "prometheus@..."},
{ id = "RUSTSEC-2024-0437", reason = "...(explanation)...", from = "opentelemetry-prometheus@..."},
]
I am currently just ignoring the issue, but that leaves the other other crates (transitive or not) open to accidentally pull in the vulnerable protobuf version in the future.
Additional context
I saw a similar issue was filed in #345 , but I think this use-case is different enough to warrant a separate issue (if only to document the reasons not to do it)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I have a transitive dependency on the Protobuf crate, which is currently affected by RUSTSEC-2024-0437
It is not likely that the upstreams (prometheus, opentelemetry-prometheus) will update the dependency in the next little while (as they are not directly vulnerable), but I would not want to "perma-ignore" the issue. As it is currently used by the upstream dependencies it seems to be harmless, but I wouldn't want it to be pulled in accidentally by some new code or dependency.
Describe the solution you'd like
I would like the ability to ignore the issue until the upstreams have had a chance to repair.
It would be nice if I could either
Currently I am adding something like this
I would like to be able to add something like (the actual vulnerable crate is
protobuf
, but I only want to allow theprometheus
andopentelemetry-prometheus
to use the vulnerable version)and/or
Describe alternatives you've considered
I am currently just ignoring the issue, but that leaves the other other crates (transitive or not) open to accidentally pull in the vulnerable protobuf version in the future.
Additional context
I saw a similar issue was filed in #345 , but I think this use-case is different enough to warrant a separate issue (if only to document the reasons not to do it)
The text was updated successfully, but these errors were encountered: