Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by Stratoscope on Wednesday December 11, 2019 @11:35PM
(#21769295)
> As I was reading the article, I found the author mentioned some of the dorks for Jenkins and Sonarqube.
I wonder if anyone could explain what "dork" means in this context? My searches are only finding the common derogatory meaning, e.g. "a socially inept person."
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by andimm on Thursday December 12, 2019 @07:11AM
(#21771157)
I found this small explanation
> Google “Dorking” is the practice of using Google to find vulnerable web applications and servers by using native Google search engine capabilities. [0]
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by dirkf on Thursday December 12, 2019 @08:03AM
(#21771465)
It doesn't necessarily have to be the case.
I've contributed a few small patches to some well-known open-source projects. In the months after that I've received a few automated mails from some CI systems informing me about some (un)successful build. Probably because somewhere somebody integrated a new version of said open-source projects in their product and the system is configured to mail every committer the outcome of the CI pipeline, regardless of whether that committer is actually an employee...
Still sloppy ops though.
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by nineteen999 on Thursday December 12, 2019 @01:27AM
(#21769720)
Also, there's a Jenkins Mask Passwords plugin which we use in conjunction with not exposing our Jenkins server to the Internet. Plus its worthwhile wrapping Jenkins with TLS.
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by cldellow on Thursday December 12, 2019 @11:28AM
(#21773269)
+1. Jenkins even has an authenticated mode, but their code quality is so inconsistent that even that's not enough.
When we investigated in 2015, we found an average of 3 remote code execution / escalation of privilege CVEs per year in the previous 4 years. Looking at [1], I see the trend is still not great - 30 CVEs in 2018.
Fundamentally, it seems to me that Jenkins does not have the mindset to do security well. This isn't surprising given its plugin architecture permits random code to run. Isolate it behind a proxy server like https://github.com/pusher/oauth2_proxy and sleep better at night.
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by Avamander on Thursday December 12, 2019 @09:53AM
(#21772271)
Set up a network, don't make it public. Block everything incoming except your VPN tunnel should you need remote access. That's how a private network works.
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by oblio on Thursday December 12, 2019 @09:53AM
(#21772268)
The easy way is to set up some sort of router, most of them NAT and block port forwarding. That way you can only access your Jenkins from the local network.
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by o-__-o on Thursday December 12, 2019 @01:16AM
(#21769670)
The only thing that keeps popping into my mind as I read this: is it illegal to hack foreign computer systems?
What are the varying levels of legality? (e.g. hacking a French company would see you extradited, hacking Iran/North Korea could bring Federal charges, but Russia.. China..?)
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by kube-system on Thursday December 12, 2019 @01:58AM
(#21769840)
There are enough laws in most places thoroughly covering these kinds of activities that you can safely assume it’s breaking at least some law in some jurisdiction.
And even if you wouldn’t be in the jurisdiction that prohibits it and/or wouldn’t be extradited for it, that doesn’t technically make it legal.
Re:Mind your Logs: How a build log from a Jenkins leaked eve...
by thenewnewguy on Thursday December 12, 2019 @01:58AM
(#21769844)
Most laws don't care about the nationality of the victim - i.e. in a legal sense yes it is illegal. Whether or not the governments would work together to extradite/charge you, on the other hand, is a different story.
I wonder if anyone could explain what "dork" means in this context? My searches are only finding the common derogatory meaning, e.g. "a socially inept person."
https://www.wsj.com/articles/a-hacker-and-the-perils-of-dork...
https://pentestmag.com/zeus-scanner-advanced-dork-searching/
https://github.com/E4rr0r4/XGDork
https://github.com/GuestGuri/dork-scanner
https://www.darknet.org.uk/2017/10/sqliv-sql-injection-dork-...
> Google “Dorking” is the practice of using Google to find vulnerable web applications and servers by using native Google search engine capabilities. [0]
[0] https://securitytrails.com/blog/google-hacking-techniques
Serves them right for such sloppy ops
I've contributed a few small patches to some well-known open-source projects. In the months after that I've received a few automated mails from some CI systems informing me about some (un)successful build. Probably because somewhere somebody integrated a new version of said open-source projects in their product and the system is configured to mail every committer the outcome of the CI pipeline, regardless of whether that committer is actually an employee... Still sloppy ops though.
I'm talking about non-firewalled open ports on a jenkins server connected to the public internet.
You're talking on about some auto-emails and a bug where too many committers were emailed.
How are those things even remotely related?
https://wiki.jenkins.io/display/JENKINS/Mask+Passwords+Plugi...
When we investigated in 2015, we found an average of 3 remote code execution / escalation of privilege CVEs per year in the previous 4 years. Looking at [1], I see the trend is still not great - 30 CVEs in 2018.
Fundamentally, it seems to me that Jenkins does not have the mindset to do security well. This isn't surprising given its plugin architecture permits random code to run. Isolate it behind a proxy server like https://github.com/pusher/oauth2_proxy and sleep better at night.
[1] https://www.cvedetails.com/vulnerability-list/vendor_id-1586...
With the slight caveat that you should have at least a second out-of-band access method for when you bork your VPN config :)
What are the varying levels of legality? (e.g. hacking a French company would see you extradited, hacking Iran/North Korea could bring Federal charges, but Russia.. China..?)
And even if you wouldn’t be in the jurisdiction that prohibits it and/or wouldn’t be extradited for it, that doesn’t technically make it legal.
If $SOMETHING is not a crime in one of the countries you can be liable for damages only, buy I am not sure if this is sufficient to be extradited.