Page History
English |
---|
Contents |
German |
---|
Inhalte |
Table of Contents |
---|
Page properties | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Advanced Panelbox | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Looking for information about bitvoodoo apps? Look here. |
English | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dear customer, On Thursday 9th December, developers and security researchers found a security vulnerability in Apache Log4j 2. Update : Atlassian put out a Security Advisory for this exploit under here: Multiple Products Security Advisory - Log4j Vulnerable To Remote Code Execution - CVE-2021-44228. Update : Atlassian updated the Security Advisory to inform about a finding that shows that some Bitbucket Data Center and Server Versions are affected. We created a info page on here: Bitbucket under Bitbucket Security Advisory - 2021-12-16. Update : Atlassian updated their FAQ with information regarding CVE 2021-45046, see here: FAQ for CVE-2021-44228 and CVE-2021-45046. Update : Atlassian updated their FAQ with information regarding CVE-2021-45105, see here: FAQ for CVE-2021-44228, CVE-2021-45046 and CVE-2021-45105. What you need to knowA security vulnerability was discovered in Apache Log4j 2. Log4j is a popular logging package for Java. This is a security issue affecting a broad range of software based upon Java. Atlassian products such as Jira and Confluence run on Java and also utilize Log4j. Atlassian products
All other Server & Data Center ProductstipData Center and Server ProductsMost Atlassian on-premise applications use an outdated version of Log4j and are not affected.Some self managed products use an Atlassian-maintained fork of Log4j 1.2.17, which is not vulnerable toaffected if you didn't modify Log4j yourself. See FAQ for CVE-2021-44228 . We have done additional analysis on this fork and confirmed a new but similar vulnerability that can only be exploited by a trusted party. For that reason, Atlassian rates the severity level for all other self-managed products as low.Cloud ProductsCloud ProductstipAtlassian secured their cloud products and has not identified compromised systems. The on-demad applications and are not affected. This vulnerability has been mitigated for all Atlassian cloud products previously using vulnerable versions of Log4j. To date, our analysis has not identified compromise of Atlassian systems or customer data prior to the patching of these systems. Atlassian customers are not vulnerable, and no action is requiredSee FAQ for CVE-2021-44228 and CVE-2021-45046. What should I do? Warning |
Further RecommendationPlease check all Java based software, beside Atlassian products, running in your organisation as this is a serious security risk. Further Reading
SupportIf you still have questions or concerns regarding this advisory, please contact the bitvoodoo support via support.bitvoodoo.ch. |
German | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sehr geehrte Kunden, am Donnerstag, den 9. Dezember, haben Entwickler und Sicherheitsforscher eine Sicherheitslücke in Apache Log4j 2 entdeckt. Update : Atlassian hat ein Security Advisory für diese Schwachstelle veröffentlicht unter , siehe hier: Multiple Products Security Advisory - Log4j Vulnerable To Remote Code Execution - CVE-2021-44228. Update : Atlassian hat das Security Advisory aktualisiert, um über einen Fund zu informieren, der zeigt, dass einige Bitbucket-Versionen betroffen sind. Wir haben eine Seite für Bitbucket erstellt unter Info-Seite, siehe hier: Bitbucket Security Advisory - 2021-12-16. Update : Atlassian hat die FAQ mit Informationen zu CVE 2021-45046 erweitert, siehe hier: FAQ for CVE-2021-44228 and CVE-2021-45046. Update : Atlassian hat die FAQ mit Informationen zu CVE-2021-45105 erweitert, siehe hier: FAQ for CVE-2021-44228, CVE-2021-45046 and CVE-2021-45105. Was Sie wissen müssenIn Apache Log4j 2 wurde eine Sicherheitslücke entdeckt. Log4j ist ein beliebtes Protokollierungspaket für Java. Es handelt sich um ein Sicherheitsproblem, das eine breite Palette von Software betrifft, die auf Java basiert. Atlassian-Produkte wie Jira und Confluence laufen auf Java und nutzen ebenfalls Log4j. Atlassian-ProdukteBitbucketServer &Data Center und Server
All other Server & Data Center Products Tip | Alle anderen Data Center und Server ProdukteDie meisten Atlassian On-Premise-Anwendungen verwenden eine veraltete Version von Log4j und sind daher nicht betroffen. Some self managed products use an Atlassian-maintained fork of Log4j 1.2.17, which is not vulnerable toSiehe FAQ for CVE-2021-44228 . We have done additional analysis on this fork and confirmed a new but similar vulnerability that can only be exploited by a trusted party. For that reason, Atlassian rates the severity level for all other self-managed products as low.Cloud Produkte Cloud ProduktetipAtlassian hat die Cloud Produkte abgesichert und konnte keine kompromittierten Systeme feststellen. Die On-Demad-Anwendungen sind nicht betroffen. This vulnerability has been mitigated for all Atlassian cloud products previously using vulnerable versions of Log4j. To date, our analysis has not identified compromise of Atlassian systems or customer data prior to the patching of these systems. Atlassian customers are not vulnerable, and no action is requiredSiehe FAQ for CVE-2021-44228 and CVE-2021-45046. Was soll ich unternehmen?
Weitergehende Empfehlung Bitte überprüfen Sie alle Java-basierte Software, die in Ihrer Organisation betrieben wird, da Log4Shell ein ernstes Sicherheitsrisiko darstellt. Weitere Informationen zum Thema
SupportWenn Sie noch Fragen oder Bedenken zu diesem Advisory haben, wenden Sie sich bitte an den bitvoodoo Support via support.bitvoodoo.ch. |