Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-7029048

(launcher) fence the launcher against LD_LIBRARY_PATH

    Details

    • Subcomponent:
    • Resolved In Build:
      b140
    • CPU:
      generic
    • OS:
      generic
    • Verification:
      Verified

      Description

      With the purging of the LD_LIBRARY_PATH via 6367077, the JDK7 launcher is
      vulnerable to the LD_LIBRARY_PATH picked up an ambient java on the path.
      For example supposing ant is run with jdk6 to invoke a jdk7 exe say javac
      then the LD_LIBRARY_PATH settings in the parent will be available to the
      child. Due to the way the Solaris rtld works the libraries on the LLP
      will take preceded over the libraries in jdk7, thus both libraries
      could exist in the process address space, thus this will lead to
      bizarre and unpredictable error conditions. See 6913237.
      Though we are planning on Release noting this, the launcher must take
      a defensive approach.
      Ideally yes, 7021644 would be the right/ideal approach, but there seems
      to be some issues with implementing that.

      I think once the drive/path is on the LLP, the system will hit it
      with stat(2), access(2), open(2) and mmap(2) calls on it. So what we
      are doing here is adding one more stat call, more than likely it
      will be lost in translation, considering the fact that rt.jar needs
      to be loaded.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ksrini Kumar Srinivasan
                Reporter:
                ksrini Kumar Srinivasan
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: