Bug 27175 - Jenkins instance exposed to public
Summary: Jenkins instance exposed to public
Status: CLOSED INVALID
Alias: None
Product: Project Infrastructure
Classification: Unclassified
Component: Continuous Integration (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low critical
Assignee: Tomás Cohen Arazi
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-08 19:51 UTC by freddy murcury
Modified: 2022-05-14 13:06 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
jenkins4koha (135.12 KB, image/png)
2020-12-08 19:51 UTC, freddy murcury
Details

Note You need to log in before you can comment on or make changes to this bug.
Description freddy murcury 2020-12-08 19:51:59 UTC
Created attachment 114267 [details]
jenkins4koha

hi team
during recon i found here 
https://jenkins.koha-community.org/view/supported/builds 
that your jenkins instance is exposed to public which should be private.
Comment 1 Mason James 2020-12-09 00:55:55 UTC
(In reply to Furman Khan from comment #0)
> Created attachment 114267 [details]
> jenkins4koha
> 
> hi team
> during recon i found here 
> https://jenkins.koha-community.org/view/supported/builds 
> that your jenkins instance is exposed to public which should be private.

hi Furman,
the jenkins.io project has it's instances public, so we can safely follow it's example?

 https://ci.jenkins.io/computer/
 https://ci.jenkins.io/view/Projects/builds
Comment 2 Jonathan Druart 2020-12-09 12:25:51 UTC
That's the expected behaviour, why should not they be public?
Comment 3 David Cook 2020-12-11 02:02:39 UTC
I don't think that this is a genuine issue. If there is a documented security vulnerability, it should be reported as a security bug instead.