Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #30663
Closed
Open
Created Apr 08, 2017 by M. Hasbini@0xbsecContributor

User is able to bypass project issues permissions to create new issues from the api

Summary

User is able to bypass project issues permissions to create new issues from the api.

Steps to reproduce

  • Disable project issues permissions or limit it to Only team members.
  • Create a new user that isn't in the project group, and generate a new token for the api.
  • curl --request POST --header "PRIVATE-TOKEN: ..." "http://localhost:3000/api/v4/projects/1/issues?title=test"

What is the current bug behavior?

Create new issue.

What is the expected correct behavior?

Not to create an issue.

I'm on master @ 3d1cade1.

Assignee
Assign to
Time tracking