ZAP API Scan Report

Open
#552 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api, backend, security

Research direction

Start by downloading the ZAP report from GitHub Actions run 20288497121 and reviewing the listed endpoints, especially /api/v1/api-docs and /actuator/health. Then trace those routes in the Java API to identify the source of the reported headers, server errors, and content types. Done should be demonstrated by a follow-up scan showing whether the listed alerts are resolved.

Written by the indexing model from the issue text.

Description

View the following link to download the report.
RunnerID:20288497121


ZAP by Checkmarx

Dominant language
Java
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bcgov/EDUC-RULE-ENGINE-API

All issues in bcgov/EDUC-RULE-ENGINE-API

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.