Organization View Does Not Require Authentication #3057

Closed
opened 2025-11-02 04:59:08 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @muellert on GitHub (Mar 17, 2019).

  • Gitea version (or commit ref): 1.7.4
  • Git version:
  • Operating system: Linux
  • Database (use [x]):
    • [X ] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When accessing an URL for an organization, no authentication is required. This way, there is a potential information leak, as non-existent "organizations" will result in a 404.

The contained private repositories or project members are all inaccessible, though, but it would be nice if one could demand that accessing an organization also requires the user to be logged in, and possibly member of a certain group.

Screenshots

Originally created by @muellert on GitHub (Mar 17, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.7.4 - Git version: - Operating system: Linux - Database (use `[x]`): - [X ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description When accessing an URL for an organization, no authentication is required. This way, there is a potential information leak, as non-existent "organizations" will result in a 404. The contained private repositories or project members are all inaccessible, though, but it would be nice if one could demand that accessing an organization also requires the user to be logged in, and possibly member of a certain group. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/question label 2025-11-02 04:59:08 -06:00
Author
Owner

@lunny commented on GitHub (Mar 17, 2019):

That's by design for security consideration.

@lunny commented on GitHub (Mar 17, 2019): ~That's by design for security consideration.~
Author
Owner

@muellert commented on GitHub (Mar 17, 2019):

Hmm? I would prefer to be able to hide organizations from unauthenticated views. How does showing them improve security?

@muellert commented on GitHub (Mar 17, 2019): Hmm? I would prefer to be able to hide organizations from unauthenticated views. How does showing them improve security?
Author
Owner

@techknowlogick commented on GitHub (Mar 17, 2019):

@muellert in 1.8.0 you can do exactly this, hide orgs from users who are unauthenticated

@techknowlogick commented on GitHub (Mar 17, 2019): @muellert in 1.8.0 you can do exactly this, hide orgs from users who are unauthenticated
Author
Owner

@lunny commented on GitHub (Mar 18, 2019):

@muellert Forget my word, as @techknowlogick said, you could create private organizations when you upgrade to v1.8

@lunny commented on GitHub (Mar 18, 2019): @muellert Forget my word, as @techknowlogick said, you could create private organizations when you upgrade to v1.8
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3057