OSV-2021-449 json
UNKNOWN READ in std::pair<absl::lts_NUMBER_02_25::container_internal::raw_hash_set<absl::lts_NUM
published 5y ago modified 4y ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31393
``` Crash type: UNKNOWN READ Crash state: std::pair<absl::lts_NUMBER_02_25::container_internal::raw_hash_set<absl::lts_NUM tensorflow::SparseCount<long, long>::Compute tensorflow::KernelAndDeviceOp::Run ```
Is OSV-2021-449 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | — | no fix listed |
References
Sources
- OSV OSV-2021-449
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.