Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
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

Several CVEs reported for this library #30

Closed
JamesAnthonyPino opened this issue Jul 9, 2018 · 2 comments
Closed

Several CVEs reported for this library #30

JamesAnthonyPino opened this issue Jul 9, 2018 · 2 comments

Comments

@JamesAnthonyPino
Copy link

When running a NVD (National Vulnerability Database) check against this library, the following CVEs were reported for this library:

@andrm
Copy link

andrm commented Jul 10, 2018

Thank you for this report.
The CVEs seem to be reported against Apache Tika, not VorbisJava. VorbisJava is used by Tika to extract information about data that are encapsuled in the OGG format.

  1. "Command Injection Vulnerability in Apache Tika’s tika-server module" I don't see any connection to VorbisJava.
  2. " A carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's BPGParser." BPG is not part of VorbisJava.
  3. "A carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's ChmParser in versions of Apache Tika before 1.18." Seems to relate to Chm, this library deals with Ogg and the encapsulated formats, it does not know how to handle CHM, even if it would encapsuled.

Please let me know if I missed something.

@Gagravarr
Copy link
Owner

As Andreas says, these all seem to be against old versions of Apache Tika, not this library. So, for now, I'm going to close this as Incorrect / invalid report from automating tooling

This library can be used without Tika at all. You only need Apache Tika to compile the parser/detector plugins for Tika, which you then add to your existing Tika install.

We currently try to compile against the oldest possible Tika version we can, to allow as many people as possible to be able to use the latest version of the library as we can. We only bump that up if required.

However, we probably will bump the minimum to Tika 2.0 fairly soon, to incorporate the breaking changes coming there.

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

No branches or pull requests

3 participants