-
Notifications
You must be signed in to change notification settings - Fork 214
Dependency updates (CVE fixes) #106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Looking good, I’ll set aside some time to merge + release. |
|
That would be appreciated. I just started looking at what it would take to upgrade Netty, but that should probably be a different PR due to the number of code changes I've already had to do. Additional notes:
|
|
Thanks for putting this together. I'm really keen to see this merged. Unfortunately the CI process seems quite unstable at the moment (intermittently failing db tests, not sure why yet) so I'm hesitant to merge until that's addressed. I'll try to find some time soon to investigate. |
See gradle/gradle#6659 for more information Signed-off-by: Taylor Smock <[email protected]>
Jump to 7.x was not done due to usage of `maven` plugin. This needs to be migrated to `maven-publish`. `maven` was deprecated in Gradle 5.6, along with `uploadArchives`. Signed-off-by: Taylor Smock <[email protected]>
Signed-off-by: Taylor Smock <[email protected]>
Signed-off-by: Taylor Smock <[email protected]>
TreeWalker is a submodule of Checker, so inherits tabWidth. tabWidth was added to Checker in 8.19. Signed-off-by: Taylor Smock <[email protected]>
Signed-off-by: Taylor Smock <[email protected]>
Signed-off-by: Taylor Smock <[email protected]>
Signed-off-by: Taylor Smock <[email protected]>
Signed-off-by: Taylor Smock <[email protected]>
|
Hello everyone, We have recently found another vulnerability in osmosis via a scan. (Spring4Shell; CVE-2022-22965) here are the files:
Can you already say when an update of the software is planned? Kind regards Robert |
* mysql connector 8.0.28 -> 8.0.29
* Avoids potential issues when using utf8mb3 server side
* Now supports FIDO authentication (requires osmosis changes to
actually use)
* postgresql 42.3.3 -> 42.3.5
* Performance and bug fixes
* protobuf 3.19.4 -> 3.20.1
* Report original exceptions from JSON parsing
* Better guards against stack overflows
* Removes deprecated functionality from protocol compiler
* spring 5.3.18 -> 5.3.20
* Updates ASM to 9.3 (Java 19 support)
* Various bug fixes
Signed-off-by: Taylor Smock <[email protected]>
|
@GeOSMRob : I'm not certain CVE-2022-22965 affects osmosis in the configuration(s) that most users will be using. Specifically, that CVE requires the following (from the GitHub page), noting that people may work around some of the requirements:
Anything that depends upon osmosis and has all those requirements fulfilled will be affected, unless they override osmosis' dependencies. It should still be fixed though. While I don't like the conveyor belt of dependency updates, it is a necessity in today's world. But as @brettch said, "the CI process seems quite unstable at the moment", and he is not wanting merge anything until that is fixed. With that said, everything seems to be working well for me locally (it didn't use to work for me, see my comment from 2021-12-28), so that may be fixed. Anyway, with this patch series, the CVE list is: Netty is going to involve a lot of code changes, and I'll start working on that in a separate PR when this one is merged. |
|
Thanks for the comments, @tsmock. You have a much better understanding of this than I do :-) Re the CI instability, I had a lot of trouble reliably reproducing the problem and parked it due to lack of time. My suspicion was that there might be race conditions between parallel database tests but I didn't get to the bottom of it. I think I should just merge your changes and hope it makes things better and not worse. At least we have a CI process again now which will make it easier to keep an eye on things. Regarding the Netty changes, I think we should just delete those features. I created it to provide a streaming mechanism that could go below 1 minute updates. But in the many years since I wrote it I haven't heard of anybody using that feature. I'll try to take a look at this again in the next couple of days and merge it. |
A good way to find out if someone uses a feature is to remove it. 😄 I don't know anyone that uses the EDIT: It is definitely possible that this PR might fix the CI DB issues, since mysql, postgis, and postgres were all updated. |
Hehe, this is true.
Yep, that's fair enough. I think it's reasonable for me to take the position that if something has known security vulnerability issues, doesn't appear to be used, and doesn't have anybody volunteering to maintain it that we take it out. I think that's better than putting in a heap of work to upgrade something that's never used. If it's the wrong call we can restore it later.
🤞 |
|
Thanks for your patience, @tsmock . It's merged now. The GitHub Actions build failed the first time on my fork but succeeded when I re-ran it. It seems that there are still some intermittent issues but this hasn't made them worse (or better). |
|
I'm sorry to hear that. I hate intermittent issues (they are often not intermittent when debugging...) I wonder if it only fails the first time it is run? (I've got a bug for JOSM ElevationProfile where the tests fail on first run, but succeed thereafter). |
|
Yah, intermittent issues can be frustrating. It's limited to pgsnapshot tasks so the blast radius is fairly small. I'll probably put my head in the sand for now and come back to it if/when I have more time and enthusiasm. I'm not sure if there's a pattern yet. I haven't found one but I haven't been methodical in investigating it either. |
Current CVE's in dependencies
With this patch series, the CVE list drops to the following: