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
It is desirable to compute per-method hashes. This would allow to better pin-point vulnerable code, and reduce the risk somewhat that unrelated modifications obscure the presence of a vulnerable method because the hash does not match any known-vulnerable class anymore.
The text was updated successfully, but these errors were encountered:
This is a good optional feature to have and will be implemented as an optional extension in a future release of the library.
However, do note that while this valuable for extended applications of the victims fingerprinting mechanism, this information for vulnerable artifacts will not be provided by the EVD database itself. Upstream projects, mostly, do not release one-off patches and isolating security patches from one release to another is not something that is reliably automatable as thing stand.
It is desirable to compute per-method hashes. This would allow to better pin-point vulnerable code, and reduce the risk somewhat that unrelated modifications obscure the presence of a vulnerable method because the hash does not match any known-vulnerable class anymore.
The text was updated successfully, but these errors were encountered: