Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39547

Corrupt node jar cache causes node to malfunction

    XMLWordPrintable

Details

    Description

      Remoting does not check whether the cached file's checksum matches before using it[1]. User with build permission can use this to inject new classes or different class implementations/resource content manipulating the cache and waiting for agent to restart.

      This can be used for denial of service attack against nodes as they will connect to Jenkins correctly but refuse to fulfill remoting requests with strange exceptions.

      More sophisticated attack can trick agent to execute custom code and therefore produce incorrect results, try to abuse existing {{SlaveToMasterCallable}}s or generate malicious files/reports to be published on masters.

      There do not seem to be a way to load those classes to master JVM or send new callable there if slave2master security is on, AFAIK.

      [1] https://github.com/jenkinsci/remoting/blob/0d8a2af7cffa6aa5a6f2675e810b286a984af04e/src/main/java/hudson/remoting/FileSystemJarCache.java#L65-70

      Attachments

        Issue Links

          Activity

            People

              olivergondza Oliver Gondža
              olivergondza Oliver Gondža
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: