Skip to content

Mitigating Log4Shell and Other Log4j-Related Vulnerabilities

Cybersecurity and Infrastructure Security Agency (CISA), FBI, & NSA. (2021). Mitigating Log4Shell and Other Log4j-Related Vulnerabilities.

Type
Report
Intellectual base
Grey literature
Year
2021
Link
https://www.cisa.gov/news-events/cybersecurity-advisories/aa21-356a
Cited from
communication_media_studies

Cited by

1 citation across 1 artifact.

Each citation links to the sentence it supports in the citing article.

Primes

  • Complete Enumeration
    • When a widely used logging library was found critically vulnerable, organizations without complete SBOMs could not answer whether they were exposed

      This sourceDocuments the Log4j (Log4Shell, CVE-2021-44228) incident and the difficulty organizations faced determining exposure given pervasive transitive use of the library — the case for complete dependency enumeration. (Resolves needs-source-011 with a security-incident/advisory reference.)

      Supported in partVerified against the work's full text

      The advisory shows Log4Shell was critical in a pervasive library and that organizations had to inventory affected assets, but it does not mention SBOMs or say organizations could not tell if they were exposed.

      “Log4j is a Java-based logging library used in a variety of consumer and enterprise services, websites, applications, and OT products.”

      From the work's full text.

      Read by an automated reader; not a human review. How support was checked

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.

Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:d1b5fbb327c9 · see in the full table