You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any news on documentation? I cannot really figure out how to run the scanner from the top README.
Would be great if we could get a more detailed documentation on how to run it.
thx
Ok for my app I get this result, which seems great:
{
"vulns": [
{
"check_name": "Custom-Check-Authorization-12526530318979110750",
"description": "Authorization bypass detected through glance in \"./test-apps/jira-damn-vulnerable-forge-app/src/index.jsx\".",
"recommendation": "Use the authorize API _https://developer.atlassian.com/platform/forge/runtime-reference/authorize-api/_ or manually authorize the user via the product REST APIs.",
"proof": "Unauthorized API call via asApp() found via glance -> fetchIssueSummary -> SecureGlance",
"severity": "High",
"app_key": "",
"app_name": "",
"date": "2023-03-14"
}
],
"scanner": "FSRT",
"started_at": "2023-03-14T22:26:42.757408Z",
"ended_at": "2023-03-14T22:26:42.757445Z",
"scanned": [
""
],
"errors": false
}
So I assume the correct output of an OK app is errors: false AND vulns: [].
I want to implement this as GitHub Actions during my build of the app and need to know if this JSON format is stable.
Also stable releases would be helpful to run a specific version of the scanner.
Here is my GitHub Actions implementation that fails my test run if there are errors or vulnerabilities, for anyone who stumbles upon this issue:
I wrote a simple assert-fsrt-results.js file in nodejs to assert the JSON test Results:
const results = require('./fsrt-scanner-result.json');
if (results.errors !== false) {
console.log( "FSRT has errors!");
process.exit(2);
}
if (results.vulns.length > 0) {
console.log( "FSRT has vulnerabilities!");
process.exit(2);
}
console.log("FRST no errors and no vulnerabilities");
It would be great to get a precompiled version of FSRT in form of a GitHub action runner ...
No description provided.
The text was updated successfully, but these errors were encountered: