Versions Compared

Old Version 3

changes.mady.by.user EBERHARD, Sebastian (messageconcept)

Saved on

compared with

New Version 4

changes.mady.by.user Christoph Schmidt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Is PeopleSync affected?

\uD83C\uDF31 Solution

No. , PeopleSync is not affected.

Product

Vulnerable

Reason

PeopleSync Backend

No

The Backend is written in .net. We are not using log4j.

For logging, we are using log4net, which is a port of log4j to the .net framework. Due to the absence of JNDI in .net, it is not possible to exploit Log4Shell in log4net.

PeopleSync Frontend

No

The Frontend is written in PHP. We are not using log4j.

PeopleSync Android App

No

There are no dependencies to log4j.

(info) Other components

If you run any 3rd-party-components on your server, please check them for the vulnerability and contact the manufacturer of the software or author of the component.

We are aware of log4j being an extension of the DTS component in some versions of Microsoft SQL Server. PeopleSync neither uses nor requires DTS. As far as we can oversee this now, Microsoft is using a version of log4j, not affected by the vulnerability. Microsoft Product Support Services will help you to remove or update the component if required.

...