[ 
https://issues.apache.org/jira/browse/UNOMI-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber reassigned UNOMI-1049:
----------------------------------

    Assignee: Serge Huber

> Embed json-patch in the services bundle and stop deploying Guava 16
> -------------------------------------------------------------------
>
>                 Key: UNOMI-1049
>                 URL: https://issues.apache.org/jira/browse/UNOMI-1049
>             Project: Apache Unomi
>          Issue Type: Improvement
>    Affects Versions: unomi-3.0.0, unomi-3.0.1
>            Reporter: Serge Huber
>            Assignee: Serge Huber
>            Priority: Major
>             Fix For: unomi-4.0.0
>
>
> _In short_
> Unomi is stuck on json-patch 1.10 because newer jars don't export their OSGi 
> packages, and that old version drags in the Guava 16.0.1 bundle, which has 
> known CVEs. Embedding json-patch in the services bundle lets us upgrade it 
> and drop Guava from the feature.
> _Details_
> * json-patch 1.11+ has no Export-Package header, so deploying it as a bundle 
> breaks the services bundle wiring (Dependabot PR #948 fails Karaf feature 
> verification).
> * PatchServiceImpl is the only user, so the library can live inside the 
> services bundle.
> * json-patch 1.13 and jackson-coreutils 2.0 no longer need Guava; no other 
> feature bundle imports it, so the Guava 16.0.1 bundle (CVE-2018-10237, 
> CVE-2020-8908, CVE-2023-2976) can be removed.
> _Fix and test_
> Embed json-patch 1.13 (with jackson-coreutils 2.0, msg-simple, btf) in 
> services and remove those bundles and Guava from the feature. New 
> PatchServiceImplTest covers JSON-Patch application; PatchIT covers it in 
> Karaf.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to