Summary of the AWS Service Event in the Northern Virginia (US-East-1) Region

Re:Summary of the AWS Service Event in the Northern Virginia... by shagie on Friday December 10, 2021 @08:57PM (#29517689)

Consider the possible ways for a string to be injected into any of the following:

  Apache Solr
  Apache Druid
  Apache Flink
  ElasticSearch
  Flume
  Apache Dubbo
  Logstash
  Kafka

If you've got any of them, they're likely exploitable too.

That list comes from: https://unit42.paloaltonetworks.com/apache-log4j-vulnerabili...

The attack surface is quite a bit larger than many realize. I recently had a conversation with a person who wasn't at a Java shop so wasn't worried... until he said "oh, wait, ElasticSearch is vulnerable too?"

You'll even see it in things like the connector between CouchBase and ElasticSearch ( https://forums.couchbase.com/t/ann-elasticsearch-connector-4... ).

[ Parent | on HN ]

Re:Summary of the AWS Service Event in the Northern Virginia... by Fordec on Friday December 10, 2021 @09:03PM (#29517721)

Lets see...

Nope. Nope. Nope. Nope. Nope. Nope. Nope.

aaaand...

Nope. Plans for it, but not yet in production.

Oh and before anyone starts, not in transitive dependencies either. Just good old bare metal EC2 instances without vendor lock in.

[ Parent | on HN ]

Re:Summary of the AWS Service Event in the Northern Virginia... by EdwardDiego on Friday December 10, 2021 @09:03PM (#29517718)

Kafka is still on log4j1. It's only vulnerable if you're using a JMSAppender.

[ Parent | on HN ]

Re:Summary of the AWS Service Event in the Northern Virginia... by log4shell on Sunday December 12, 2021 @01:18PM (#29532045)

Kafka is not vulnerable for this particular exploit but hdfs kafka connect plugin is.

[ Parent | on HN ]