Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. WordPress (Developer)
  3. Jetpack alerting on security vuln

Jetpack alerting on security vuln

Scheduled Pinned Locked Moved WordPress (Developer)
7 Posts 4 Posters 959 Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • ianhyzyI Offline
    ianhyzyI Offline
    ianhyzy
    wrote on last edited by
    #1

    Jetpack is warning me about this - do I need to worry about it? I moved from a different host (back) to cloudron and don't recall seeing this before

    cc4a21d8-65dc-4a13-9aa2-a8fae53ad093-image.png

    1 Reply Last reply
    0
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      That's quite an abstract threat message 🙂 Can't say I understand it. @ianhyzy Can you post the link in the screenshot? (The technical details link)

      ianhyzyI 1 Reply Last reply
      1
      • girishG girish

        That's quite an abstract threat message 🙂 Can't say I understand it. @ianhyzy Can you post the link in the screenshot? (The technical details link)

        ianhyzyI Offline
        ianhyzyI Offline
        ianhyzy
        wrote on last edited by ianhyzy
        #3

        @girish yup, here you go https://wpscan.com/vulnerability/c8814e6e-78b3-4f63-a1d3-6906a84c1f11

        girishG 1 Reply Last reply
        0
        • ianhyzyI ianhyzy

          @girish yup, here you go https://wpscan.com/vulnerability/c8814e6e-78b3-4f63-a1d3-6906a84c1f11

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #4

          @ianhyzy I think that link is saying that there is no known fix. https://www.sonarsource.com/blog/wordpress-core-unauthenticated-blind-ssrf/ says similar. Looks like quite a recent report.

          jdaviescoatesJ 1 Reply Last reply
          1
          • girishG girish

            @ianhyzy I think that link is saying that there is no known fix. https://www.sonarsource.com/blog/wordpress-core-unauthenticated-blind-ssrf/ says similar. Looks like quite a recent report.

            jdaviescoatesJ Offline
            jdaviescoatesJ Offline
            jdaviescoates
            wrote on last edited by
            #5

            @girish said in Jetpack alerting on security vuln:

            @ianhyzy I think that link is saying that there is no known fix. https://www.sonarsource.com/blog/wordpress-core-unauthenticated-blind-ssrf/ says similar. Looks like quite a recent report.

            also seems to say this issue by itself isn't much to worry about

            We couldn't generically identify ways to leverage this behavior to take over vulnerable instances without relying on other vulnerable services.

            and

            We've audited the code in the hope of finding parser differential bugs that would allow reaching unintended ports or performing POST requests without success: the initial URL validation steps are restrictive enough to prevent their exploitation. As mentioned earlier, attackers would have to chain this behavior with another vulnerability to impact the targeted organization's security significantly.

            I use Cloudron with Gandi & Hetzner

            1 Reply Last reply
            0
            • ianhyzyI Offline
              ianhyzyI Offline
              ianhyzy
              wrote on last edited by
              #6

              thanks, should have read that more clearly - will just ignore it!

              C 1 Reply Last reply
              1
              • ianhyzyI ianhyzy

                thanks, should have read that more clearly - will just ignore it!

                C Offline
                C Offline
                ccfu
                wrote on last edited by ccfu
                #7

                @ianhyzy
                Update to 6.2 and that message should go away. Other control panels reported this as well but WP saw no need to act on it as there was no likely risk of it being exploited.

                1 Reply Last reply
                3
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search