Skip to content

Conversation

@akhilyendluri
Copy link

Parquet version older than 1.15.1 have a security issue. CVE: https://nvd.nist.gov/vuln/detail/CVE-2025-30065

Parquet version older than 1.15.1 have a security issue.
CVE: https://nvd.nist.gov/vuln/detail/CVE-2025-30065
@nastra nastra changed the title Updating parquet dependency (#12749) [1.8.x] Build: Bump Parquet from 1.15.0 to 1.15.1 (#12749) Apr 11, 2025
@pvary pvary merged commit 69fa6aa into apache:1.8.x Apr 11, 2025
46 checks passed
@pvary
Copy link
Contributor

pvary commented Apr 11, 2025

Sorry, I merged this with the wrong commit message (somehow the PR name was not changed the merged commit message automatically), but at least it is in the 1.8.x branch now.
Thanks @akhilyendluri for the PR, and @nastra for the review!

akhilyendluri pushed a commit to akhilyendluri/iceberg that referenced this pull request Apr 11, 2025
Parquet version older than 1.15.1 have a security issue.
CVE: https://nvd.nist.gov/vuln/detail/CVE-2025-30065
@manuzhang
Copy link
Member

Do we need to update LICENSE and NOTICE as well?

@pvary
Copy link
Contributor

pvary commented Apr 14, 2025

Do we need to update LICENSE and NOTICE as well?

@manuzhang: You are right. Would you mind creating the PR, so I can merge it?

Thanks,
Peter

@rdblue
Copy link
Contributor

rdblue commented Apr 14, 2025

Do we need to update LICENSE and NOTICE as well?

If we do, please remove the version numbers from the LICENSE and NOTICE. We should not need to update them for every patch release!

@manuzhang
Copy link
Member

If we do, please remove the version numbers from the LICENSE and NOTICE.

@jbonofre WDYT?

@nastra nastra added this to the Iceberg 1.8.2 milestone Apr 16, 2025
@jbonofre
Copy link
Member

jbonofre commented Apr 16, 2025

Yeah, I proposed to remove version in the past to avoid any LICENSE/NOTICE issue, even I think it's better to document version (as LICENSE/NOTICE can change from a version to another). So I'm fine removing it.
For context, it's important to keep the version for BSD/MIT dependency as licenses sometimes change as product version change.
For Apache dependencies, assuming that the bundled dependency itself contains no bundled sub-components under other licenses, so the ALv2 applies uniformly to all files, there is no need to modify LICENSE. However, for completeness it is useful to list the products and their versions, as is done for products under other licenses.
So, I think for this update, it's important information to keep.

@manuzhang
Copy link
Member

@jbonofre Thanks for your thoughts. Maybe we can do a one time change when a dependency's license change. I've opened a PR to remove the versions in LICENSE on 1.8.x branch. Please help review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants