Comments (2)
rsenden
commented on August 16, 2024
Hi, thanks for reporting this. According to the screenshot below, the sample file that you provided validates successfully against the GitLab DAST JSON schema, so I'm not sure why you are getting this error. Without further details on why the parsing is failing, I won't be able to investigate this further and/or provide a fix.
Can you please report this issue to GitLab, to have them investigate why parsing fails even though the artifact validates fine against the JSON schema? Based on their feedback, please let me know whether anything needs to be changed in FortifyBugTrackerUtility.
from fortifyvulnerabilityexporter.
rsenden
commented on August 16, 2024
After consultation with the GitLab team, various work-arounds have been implemented to allow GitLab reports to be ingested successfully.
from fortifyvulnerabilityexporter.
Related Issues (20)
- javax.validation.ConstraintDeclarationException: HV000170: No JSR-223 scripting engine could be bootstrapped for language "javascript HOT 2
- Add documentation section for BitBucket integration HOT 3
- How to disable SSC URL link within GITLAB-SSC integration using Vulnerability Exporter container. HOT 2
- Backstage Plugin HOT 3
- Dockerfile HOT 1
- How to add comments to Gitlab SSC output using custom config? HOT 2
- SSC to Bitbucket config is not working as expected HOT 2
- GitLab: Update schema version
- Add Debricked as SCA option HOT 1
- How to filter for all 10 'OWASP Top 10 2017' in SSC HOT 3
- How to add the actual code snippets for each vulnerability when exporting to Json or Csv? HOT 6
- includeSuppressed HOT 2
- JSON Raw format export issue of Java 8 date/time type
- How to export vulnerabilities to GitHub Security from a local file system (i.e. not using SSC) HOT 2
- Invalid line numbers in GitHub SARIF output under `codeFlows` HOT 2
- fortify-vulnerability-exporter unable to generate report for GitLab HOT 2
- Fail on unknown command-line arguments
- Reconsider ability to process all releases for matching app(s) when using `fod.release.name`/`ssc.version.name` properties
- Fortify SCA SARIF inaccuracy causing poor GitHub Code Scanning experience HOT 17
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fortifyvulnerabilityexporter.