<html>
    <head>
      <base href="https://bugs.documentfoundation.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_UNCONFIRMED "
   title="UNCONFIRMED - JURT and JUH JARs contain bad class path declaration"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=134248">134248</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>JURT and JUH JARs contain bad class path declaration
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>LibreOffice
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>UNCONFIRMED
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>sdk
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>libreoffice-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>alexander.veit@unitedplanet.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>This is actually two bugs. The most serious is

1.) The Class-Path declaration in the respective META-INF/MANIFEST.MF files
contains ../ as an entry. This does not make sense and has the potential to
screw up IDEs and runtime deployments by adding completely unrelated parts of
the file system to the class path[1]. It may also qualify as a security issue.

2.) Class-Path also contains entries like "ridl.jar unoloader.jar". This does
not make sense either. These JARs normally do not extist since they are usually
distributed[2] with a version suffix in the file name, e.g. ridl-6.4.3.jar.

The best solution to solve this issue is probably to remove the Class-Path
entry from the MANIFEST.MF files altogether.


[1] <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=563819">https://bugs.eclipse.org/bugs/show_bug.cgi?id=563819</a>
[2] <a href="https://repo1.maven.org/maven2/org/libreoffice/juh/6.4.3/">https://repo1.maven.org/maven2/org/libreoffice/juh/6.4.3/</a></pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>