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
We pull in the vulnerable version via chrono 0.4.23. Even if we turn off the oldtime feature, other things in our tree depend on chrono and use that feature. I think the way forward is to wait for a chrono release that doesn't depend on time. Fortunately, this is already the case in their upcoming 0.5 release, but I don't know when that will come out.
We got a security advisory on the
time
crate: https://github.com/divviup/janus/security/dependabot/9We pull in the vulnerable version via
chrono 0.4.23
. Even if we turn off theoldtime
feature, other things in our tree depend onchrono
and use that feature. I think the way forward is to wait for achrono
release that doesn't depend ontime
. Fortunately, this is already the case in their upcoming 0.5 release, but I don't know when that will come out.In the meantime, the chrono maintainers assure us that chrono doesn't use the vulnerable APIs from
time
, so I don't think we need to do anything.The text was updated successfully, but these errors were encountered: