[jira] [Assigned] (OAK-9987) Oak-search-elastic depends on vulnerable snakeyaml version.
[ https://issues.apache.org/jira/browse/OAK-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria reassigned OAK-9987: -- Assignee: Mohit Kataria > Oak-search-elastic depends on vulnerable snakeyaml version. > --- > > Key: OAK-9987 > URL: https://issues.apache.org/jira/browse/OAK-9987 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Affects Versions: 1.44.0 >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > > Description: oak-search-elastic embeds snakeyaml-1.26.jar which is vulnerable > to > CVE-2022-38749MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38750MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-25857MEDIUM The package org.yaml:snakeyaml from 0 and > before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested > depth limitation for collections. > CVE-2022-38751MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38752MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stack-overflow. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9988) MergeRunnerTest leaves temp files/folders behind
Julian Reschke created OAK-9988: --- Summary: MergeRunnerTest leaves temp files/folders behind Key: OAK-9988 URL: https://issues.apache.org/jira/browse/OAK-9988 Project: Jackrabbit Oak Issue Type: Bug Components: run Reporter: Julian Reschke Assignee: Amit Jain ...might be just missing test cleanup. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9987) Oak-search-elastic depends on vulnerable snakeyaml version.
[ https://issues.apache.org/jira/browse/OAK-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630361#comment-17630361 ] Mohit Kataria commented on OAK-9987: elasticsearch-x-content depends on vulnerable snakeyaml. But as we are now using java client instead, we can remove elasticsearch-x-content from pom. > Oak-search-elastic depends on vulnerable snakeyaml version. > --- > > Key: OAK-9987 > URL: https://issues.apache.org/jira/browse/OAK-9987 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Affects Versions: 1.44.0 >Reporter: Mohit Kataria >Priority: Major > > Description: oak-search-elastic embeds snakeyaml-1.26.jar which is vulnerable > to > CVE-2022-38749MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38750MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-25857MEDIUM The package org.yaml:snakeyaml from 0 and > before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested > depth limitation for collections. > CVE-2022-38751MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38752MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stack-overflow. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9987) Oak-search-elastic depends on vulnerable snakeyaml version.
[ https://issues.apache.org/jira/browse/OAK-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria updated OAK-9987: --- Affects Version/s: 1.44.0 > Oak-search-elastic depends on vulnerable snakeyaml version. > --- > > Key: OAK-9987 > URL: https://issues.apache.org/jira/browse/OAK-9987 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Affects Versions: 1.44.0 >Reporter: Mohit Kataria >Priority: Major > > Description: oak-search-elastic embeds snakeyaml-1.26.jar which is vulnerable > to > IDCVSSSummary > CVE-2022-38749MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38750MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-25857MEDIUM The package org.yaml:snakeyaml from 0 and > before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested > depth limitation for collections. > CVE-2022-38751MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38752MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stack-overflow. > Recommendation: > Apply one of the following suggestions: > Remove usage and dependency > Upgrade to a vulnerability free version of the embedded library. If none is > available, upgrade to a less vulnerable version (lower CVSS Score) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9987) Oak-search-elastic depends on vulnerable snakeyaml version.
[ https://issues.apache.org/jira/browse/OAK-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria updated OAK-9987: --- Description: Description: oak-search-elastic embeds snakeyaml-1.26.jar which is vulnerable to ID CVSSSummary CVE-2022-38749 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-38750 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-25857 MEDIUM The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections. CVE-2022-38751 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-38752 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow. Recommendation: Apply one of the following suggestions: Remove usage and dependency Upgrade to a vulnerability free version of the embedded library. If none is available, upgrade to a less vulnerable version (lower CVSS Score) > Oak-search-elastic depends on vulnerable snakeyaml version. > --- > > Key: OAK-9987 > URL: https://issues.apache.org/jira/browse/OAK-9987 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Mohit Kataria >Priority: Major > > Description: oak-search-elastic embeds snakeyaml-1.26.jar which is vulnerable > to > IDCVSSSummary > CVE-2022-38749MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38750MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-25857MEDIUM The package org.yaml:snakeyaml from 0 and > before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested > depth limitation for collections. > CVE-2022-38751MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38752MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stack-overflow. > Recommendation: > Apply one of the following suggestions: > Remove usage and dependency > Upgrade to a vulnerability free version of the embedded library. If none is > available, upgrade to a less vulnerable version (lower CVSS Score) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9987) Oak-search-elastic depends on vulnerable snakeyaml version.
[ https://issues.apache.org/jira/browse/OAK-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria updated OAK-9987: --- Description: Description: oak-search-elastic embeds snakeyaml-1.26.jar which is vulnerable to CVE-2022-38749 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-38750 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-25857 MEDIUM The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections. CVE-2022-38751 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-38752 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow. was: Description: oak-search-elastic embeds snakeyaml-1.26.jar which is vulnerable to ID CVSSSummary CVE-2022-38749 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-38750 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-25857 MEDIUM The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections. CVE-2022-38751 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. CVE-2022-38752 MEDIUM Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow. Recommendation: Apply one of the following suggestions: Remove usage and dependency Upgrade to a vulnerability free version of the embedded library. If none is available, upgrade to a less vulnerable version (lower CVSS Score) > Oak-search-elastic depends on vulnerable snakeyaml version. > --- > > Key: OAK-9987 > URL: https://issues.apache.org/jira/browse/OAK-9987 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Affects Versions: 1.44.0 >Reporter: Mohit Kataria >Priority: Major > > Description: oak-search-elastic embeds snakeyaml-1.26.jar which is vulnerable > to > CVE-2022-38749MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38750MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-25857MEDIUM The package org.yaml:snakeyaml from 0 and > before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested > depth limitation for collections. > CVE-2022-38751MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stackoverflow. > CVE-2022-38752MEDIUM Using snakeYAML to parse untrusted YAML files > may be vulnerable to Denial of Service attacks (DOS). If the parser is > running on user supplied input, an attacker may supply content that causes > the parser to crash by stack-overflow. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9987) Oak-search-elastic depends on vulnerable snakeyaml version.
Mohit Kataria created OAK-9987: -- Summary: Oak-search-elastic depends on vulnerable snakeyaml version. Key: OAK-9987 URL: https://issues.apache.org/jira/browse/OAK-9987 Project: Jackrabbit Oak Issue Type: Improvement Components: indexing Reporter: Mohit Kataria -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9958) Deprecate native queries
[ https://issues.apache.org/jira/browse/OAK-9958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630356#comment-17630356 ] Mohit Kataria commented on OAK-9958: PR: https://github.com/apache/jackrabbit-oak/pull/723 > Deprecate native queries > > > Key: OAK-9958 > URL: https://issues.apache.org/jira/browse/OAK-9958 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > > We can always use sql2/xpath queries instead of native queries. So for > elastic index, instead of supporting native queries, it makes sense to > decrease api surface and deprecate native queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9958) Deprecate native queries
[ https://issues.apache.org/jira/browse/OAK-9958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria resolved OAK-9958. Fix Version/s: 1.46.0 Resolution: Fixed > Deprecate native queries > > > Key: OAK-9958 > URL: https://issues.apache.org/jira/browse/OAK-9958 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > Fix For: 1.46.0 > > > We can always use sql2/xpath queries instead of native queries. So for > elastic index, instead of supporting native queries, it makes sense to > decrease api surface and deprecate native queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-7182) Make it possible to update Guava
[ https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630269#comment-17630269 ] Julian Reschke commented on OAK-7182: - I'm not sure yet that it is a new leakage (will have to check). We could add a verification step in the release process document - but if it relies on people actually doing manual checks, it might not be good enough. > Make it possible to update Guava > > > Key: OAK-7182 > URL: https://issues.apache.org/jira/browse/OAK-7182 > Project: Jackrabbit Oak > Issue Type: Wish >Reporter: Julian Reschke >Priority: Minor > Attachments: GuavaTests.java, OAK-7182-guava-21-3.diff, > OAK-7182-guava-21-4.diff, OAK-7182-guava-21.diff, OAK-7182-guava-23.6.1.diff, > guava.diff > > > We currently rely on Guava 15, and this affects all users of Oak because they > essentially need to use the same version. > This is an overall issue to investigate what would need to be done in Oak in > order to make updates possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-7182) Make it possible to update Guava
[ https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17629845#comment-17629845 ] Julian Reschke edited comment on OAK-7182 at 11/8/22 8:22 AM: -- Well; progress is on this issue proves to be hard. We sort-of had settled to first deprecating and then removing APIs that expose Guava objects. We were done with the deprecations, but a certain downstream project hasn't been updated yet, and doing so will take time. OTOH, we planned to revise Oak's code to use newer versions of Gauva in any case (be it directly or shadowed - both will require code changes). So my proposal is to - while we're waiting on progress on the deprecation/removal front - we actually start upgrading Guava step by step. For now that would mean moving to 19.0, which would allow us to update our code not to use those APIs that have been removed in Guava >= 20.0. Feedback appreciated. was (Author: reschke): Well; progress is on this issue proves to be hard. We sort-of had settled to first deprecating and then removing APIs that expose Guava objects. We were done with the deprecations, but a certain downstream project hasn't been updated yet, and doing so will take time. OTOH, we planned to revise Oak's code to use newer versions of Gauva in any case (be it directly or shadowed - both will require code changes). So my proposal is to - while we're waiting on progress on the deprecation/removal front - we actually start upgrading Guava step by step. For now that would mean moving to 19.0, which would allow us to update our code not to use those APIs that have been removed ib Guava >= 20.0. Feedback appreciated. > Make it possible to update Guava > > > Key: OAK-7182 > URL: https://issues.apache.org/jira/browse/OAK-7182 > Project: Jackrabbit Oak > Issue Type: Wish >Reporter: Julian Reschke >Priority: Minor > Attachments: GuavaTests.java, OAK-7182-guava-21-3.diff, > OAK-7182-guava-21-4.diff, OAK-7182-guava-21.diff, OAK-7182-guava-23.6.1.diff, > guava.diff > > > We currently rely on Guava 15, and this affects all users of Oak because they > essentially need to use the same version. > This is an overall issue to investigate what would need to be done in Oak in > order to make updates possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
