[
https://issues.apache.org/jira/browse/FLINK-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10007:
-----------------------------------
Labels: auto-deprioritized-critical stale-major (was:
auto-deprioritized-critical)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Security vulnerability in website build infrastructure
> ------------------------------------------------------
>
> Key: FLINK-10007
> URL: https://issues.apache.org/jira/browse/FLINK-10007
> Project: Flink
> Issue Type: Bug
> Components: Project Website
> Reporter: Fabian Hueske
> Priority: Major
> Labels: auto-deprioritized-critical, stale-major
>
> We've got a notification from Apache INFRA about a potential security
> vulnerability:
> {quote}
> We found a potential security vulnerability in a repository for which you
> have been granted security alert access.
> @apache apache/flink-web
> Known high severity security vulnerability detected in yajl-ruby < 1.3.1
> defined in Gemfile.
> Gemfile update suggested: yajl-ruby ~> 1.3.1.
> {quote}
> This is a problem with the build environment of the website, i.e., this
> dependency is not distributed or executed with Flink but only run when the
> website is updated.
> Nonetheless, we should of course update the dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
