{"id":3411,"date":"2021-12-14T10:22:29","date_gmt":"2021-12-14T09:22:29","guid":{"rendered":"https:\/\/fiskaltrust.eu\/news\/sicherheitsproblem-mit-log4j-bei-cloud-tse\/"},"modified":"2025-05-05T00:47:13","modified_gmt":"2025-05-04T23:47:13","slug":"sicherheitsproblem-mit-log4j-bei-cloud-tse","status":"publish","type":"news","link":"https:\/\/fiskaltrust.eu\/news\/sicherheitsproblem-mit-log4j-bei-cloud-tse\/","title":{"rendered":"Sicherheitsproblem mit log4j bei Cloud-TSE"},"content":{"rendered":"\n

Wahrscheinlich haben Sie von den anhaltenden Sicherheitsproblemen mit log4j, dem Java-Logging-Framework, geh\u00f6rt. <\/p>\n\n\n\n

fiskaltrust verwendet diese Bibliothek in keinem ihrer eigenen Produkte und somit sind nach unserem derzeitigen Kenntnisstand keine angebotenen Dienste der fiskaltrust betroffen.  <\/p>\n\n\n\n

fiskaltrust liegen bereits Informationen diverser Anbieter vor, die von dieser Sicherheitsl\u00fccke betroffen sind. Alle Anbieter arbeiten mit Hochdruck an einer L\u00f6sung.  <\/p>\n\n\n\n\n\n\n\n

SwissbitCloud und  DeutscheFiskal Benutzer mit entsprechenden SCUs haben, wie von DF\/SB vorgeschlagen, zwei M\u00f6glichkeiten, die Sicherheitsl\u00fccke zu schlie\u00dfen. <\/p>\n\n\n\n

  1. Manuelles Setzen der Umgebungsvariablen auf dem Client, der die FCC ausf\u00fchrt, wie folgt: LOG4J_FORMAT_MSG_NO_LOOKUPS=true<\/kbd><\/li>
  2. Sollte dies nicht m\u00f6glich sein, wird Benutzern empfohlen zu warten, bis die neue FCC-Version freigegeben wird. Sobald dies geschieht, wird eine neue SCU-Version ver\u00f6ffentlicht und die FCC automatisch aktualisiert. Benutzer k\u00f6nnen die Sicherheitsl\u00fccke beheben, indem sie die SCU ohne zus\u00e4tzlich notwendige Schritte aktualisieren. <\/li><\/ol>\n\n\n\n

    Wir stehen im st\u00e4ndigen Austausch mit den Anbietern und informieren sie bez\u00fcglich zu den weiteren Entwicklungen auf unserem Blog. <\/p>\n\n\n\n

    Bei weiteren Fragen wenden Sie sich bitte an sales@fiskaltrust.de<\/a>.<\/p>\n\n\n\n

    English version below:<\/h2>\n\n\n\n

    Probably you have heard of the\u202fongoing security gap with log4j, the java logging framework.  <\/p>\n\n\n\n

    fiskaltrust does not use this library in any of its own products and therefore currently no services offered by fiskaltrust are affected. <\/p>\n\n\n\n

    Furthermore fiskaltrust already has been informed and is actively requesting information from various providers who might be affected by this security gap. All providers are working out on a permanent fix. <\/p>\n\n\n\n

    SwissbitCloud and DeutscheFiskal users with appropriate SCUs have two options for closing the security gap, as suggested by DF \/ SB: <\/p>\n\n\n\n

    Users of the affected SCUs have two options, as suggested by DF\/SB: <\/p>\n\n\n\n

    1. Set the environment variable\u202fLOG4J_FORMAT_MSG_NO_LOOKUPS=true<\/kbd>\u202fmanually on the PC on which the FCC is running <\/li><\/ol>\n\n\n\n
      1. In case this is not possible, users should wait until the new FCC version is released. As soon as this happens a new SCU version that automatically updates the FCC will be released. After that users can fix the security issue by updating their SCU without any further steps. <\/li><\/ol>\n\n\n\n

        In case of any additional questions please reach out to sales@fiskaltrust.de<\/a>.\u202f <\/p>\n","protected":false},"author":1,"featured_media":3412,"parent":0,"menu_order":0,"template":"","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"","_seopress_titles_title":"Sicherheitsproblem log4j bei Cloud-TSE - fiskaltrust","_seopress_titles_desc":"Sicherheitsproblem mit log4j bei Cloud-TSE: fiskaltrust informiert H\u00e4ndler und Entwickler. Aktuelle Sicherheitsupdates f\u00fcr Kassensysteme.","_seopress_robots_index":"","footnotes":""},"news-market":[82],"news-targetgroup":[],"news-topic":[],"class_list":["post-3411","news","type-news","status-publish","has-post-thumbnail","hentry","news-market-de"],"acf":[],"wpml_current_locale":null,"wpml_translations":[],"wpml_trid":null,"_links":{"self":[{"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/news\/3411","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/news"}],"about":[{"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/types\/news"}],"author":[{"embeddable":true,"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/news\/3411\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/media\/3412"}],"wp:attachment":[{"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/media?parent=3411"}],"wp:term":[{"taxonomy":"news-market","embeddable":true,"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/news-market?post=3411"},{"taxonomy":"news-targetgroup","embeddable":true,"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/news-targetgroup?post=3411"},{"taxonomy":"news-topic","embeddable":true,"href":"https:\/\/fiskaltrust.eu\/en-eu\/wp-json\/wp\/v2\/news-topic?post=3411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}