fabricalab/streaming-flink-file-source

File source operator for Apache Flink

flink-file-source

Apache Flink® is a framework and distributed processing engine for stateful computations over unbounded and bounded data streams.
This open source project contains a Source operator that allow to retrieval file content and handling mutations. You must provide a class that represent the content file so that the operator can return a typed stream.

Maven Repository

Flink file source release are available from Maven Central. Snapshot builds are distributed using OSS Sonatype

Quick Installation

If you are using Maven you can add the flink-file-source by adding the following XML to your pom.xml file:

<dependency>
  <groupId>it.fabricalab.streaming</groupId>
  <artifactId>flink-file-source</artifactId>
  <version>1.1.0</version>
</dependency>

Documentation

All the documentation is available on the wiki pages.

Disclaimer

Apache Flink, Flink®, Apache®, the squirrel logo, and the Apache feather logo are either registered trademarks or trademarks of The Apache Software Foundation.

streaming-flink-file-source's Issues

CVE-2021-44832 (Medium) detected in log4j-core-2.13.3.jar

CVE-2021-44832 - Medium Severity Vulnerability

Vulnerable Library - log4j-core-2.13.3.jar

The Apache Log4j Implementation

Library home page: https://logging.apache.org/log4j/2.x/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.13.3/log4j-core-2.13.3.jar

Dependency Hierarchy:

• log4j-slf4j18-impl-2.13.3.jar (Root Library)
  • ❌ log4j-core-2.13.3.jar (Vulnerable Library)

Vulnerability Details

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

Publish Date: 2021-12-28

URL: CVE-2021-44832

CVSS 3 Score Details (6.6)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: High
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://logging.apache.org/log4j/2.x/security.html

Release Date: 2021-12-28

Fix Resolution (org.apache.logging.log4j:log4j-core): 2.17.1

Direct dependency fix Resolution (org.apache.logging.log4j:log4j-slf4j18-impl): 2.17.1

---

Step up your Open Source Security Game with Mend here

CVE-2021-45046 (High) detected in log4j-core-2.13.3.jar

CVE-2021-45046 - High Severity Vulnerability

Vulnerable Library - log4j-core-2.13.3.jar

The Apache Log4j Implementation

Library home page: https://logging.apache.org/log4j/2.x/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.13.3/log4j-core-2.13.3.jar

Dependency Hierarchy:

• log4j-slf4j18-impl-2.13.3.jar (Root Library)
  • ❌ log4j-core-2.13.3.jar (Vulnerable Library)

Vulnerability Details

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

Publish Date: 2021-12-14

URL: CVE-2021-45046

CVSS 3 Score Details (9.0)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://logging.apache.org/log4j/2.x/security.html

Release Date: 2021-12-14

Fix Resolution (org.apache.logging.log4j:log4j-core): 2.16.0

Direct dependency fix Resolution (org.apache.logging.log4j:log4j-slf4j18-impl): 2.16.0

---

Step up your Open Source Security Game with Mend here

CVE-2021-45105 (Medium) detected in log4j-core-2.13.3.jar

CVE-2021-45105 - Medium Severity Vulnerability

Vulnerable Library - log4j-core-2.13.3.jar

The Apache Log4j Implementation

Library home page: https://logging.apache.org/log4j/2.x/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.13.3/log4j-core-2.13.3.jar

Dependency Hierarchy:

• log4j-slf4j18-impl-2.13.3.jar (Root Library)
  • ❌ log4j-core-2.13.3.jar (Vulnerable Library)

Vulnerability Details

Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.

Publish Date: 2021-12-18

URL: CVE-2021-45105

CVSS 3 Score Details (5.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://logging.apache.org/log4j/2.x/security.html

Release Date: 2021-12-18

Fix Resolution (org.apache.logging.log4j:log4j-core): 2.17.0

Direct dependency fix Resolution (org.apache.logging.log4j:log4j-slf4j18-impl): 2.17.0

---

Step up your Open Source Security Game with Mend here

CVE-2021-44228 (High) detected in log4j-core-2.13.3.jar

CVE-2021-44228 - High Severity Vulnerability

Vulnerable Library - log4j-core-2.13.3.jar

The Apache Log4j Implementation

Library home page: https://logging.apache.org/log4j/2.x/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/logging/log4j/log4j-core/2.13.3/log4j-core-2.13.3.jar

Dependency Hierarchy:

• log4j-slf4j18-impl-2.13.3.jar (Root Library)
  • ❌ log4j-core-2.13.3.jar (Vulnerable Library)

Vulnerability Details

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

Publish Date: 2021-12-10

URL: CVE-2021-44228

CVSS 3 Score Details (10.0)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://logging.apache.org/log4j/2.x/security.html

Release Date: 2021-12-10

Fix Resolution (org.apache.logging.log4j:log4j-core): 2.15.0

Direct dependency fix Resolution (org.apache.logging.log4j:log4j-slf4j18-impl): 2.15.0

---

Step up your Open Source Security Game with Mend here