OHDSI / OHDSI/WebAPI

Critical Security Vulnerability in Apache Log4j (CVE-2021-45046) Affecting WebAPI

Open
#2,479 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
151
Forks
183
Avg merge
14m
Merged PRs (30d)
2

Description

We have detected a critical security vulnerability (CVE-2021-45046) in Apache Log4j components used by WebAPI. This vulnerability allows attackers to exploit incomplete fixes for CVE-2021-44228 in certain non-default configurations, potentially leading to Remote Code Execution (RCE) and information disclosure.

Details:

  • CVE: CVE-2021-45046
  • Severity: Critical
  • Affected Components: log4j-core versions:
    • 2.2 (WEBAPI 2.14.0 uses this version)
    • 2.13.3
    • 2.14.0
  • Exploit Availability: Confirmed

Description:

The fix for CVE-2021-44228 in Log4j 2.15.0 was incomplete. Attackers can manipulate Thread Context Map (MDC) input data when logging configuration uses non-default Pattern Layout with Context Lookup (e.g., $ {ctx:loginId}) or Thread Context Map patterns (%X, %mdc, %MDC). This can result in malicious JNDI lookups, leading to RCE or sensitive data leaks.

Recommended Fix:

  • Upgrade to patched versions:
    • 2.12.2
    • 2.16.0 (or higher)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating WebAPI's log4j-core dependency declarations and checking the resolved version against the affected 2.14.0 release. Update it to a patched version such as 2.16.0 or higher, then verify the dependency resolution and run the project's available tests and security checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.