Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[lyo-dev] An update to the Lyo statement of using Log4j2
An update to the Eclipse Lyo statement of using Log4j2: lyo.rio experimental implementations of the abandoned OSLC 3 draft (that included breaking changes that were not incorporated into the OSLC 3.0 OASIS Standard) use Log4j v2 and may be vulnerable to the recent CVEs you've all heard about.

The previous statement from the Lyo project was that no part of the project was vulnerable. lyo.rio has not been part of regular releases of Lyo and is not available from Maven Central or Eclipse Maven repositories. We expect that no Lyo users use lyo.rio in production and no further actions are needed from your side.

I just merged the PR from the bot, you can check the diff to see if you are using the affected artifact:

<dependency>
    <groupId>org.eclipse.lyo.oslc4j.rio</groupId>
    <artifactId>oslc-v3-rio</artifactId>
    <packaging>war</packaging>
    <version>4.0.0-SNAPSHOT</version>
</dependency>

/Andrew

Begin forwarded message:

From: "dependabot[bot]" <notifications@xxxxxxxxxx>
Subject: [eclipse/lyo.rio] Bump log4j-core from 2.15.0 to 2.17.0 in /rio-oslc3/org.eclipse.lyo.oslc.v3.sample (PR #31)
Date: W50 18 December 2021 at 19:19:16 CET
To: "eclipse/lyo.rio" <lyo.rio@xxxxxxxxxxxxxxxxxx>

This automated pull request fixes a security vulnerability (high severity).

Learn more about Dependabot security updates.

Bumps log4j-core from 2.15.0 to 2.17.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

You can view, comment on, or merge this pull request online at:

  https://github.com/eclipse/lyo.rio/pull/31

Commit Summary

  • 5aac22a Bump log4j-core in /rio-oslc3/org.eclipse.lyo.oslc.v3.sample

File Changes

(1 file)

Patch Links:

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <eclipse/lyo.rio/pull/31@github.com>


Back to the top