Azure ARM scan results split into separate sections with empty target name #9059
Closed
AngryCatKR96
started this conversation in
Bugs
Replies: 2 comments
-
|
Hi @AngryCatKR96 ! Thank you for the report. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Track #9137 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
When scanning a single Azure ARM template file, Trivy splits scan results into two separate sections in the output. The first section appears with an empty target name (showing only " (azure-arm)"), while the second section correctly shows the filename ("filename.json (azure-arm)"). This creates confusion about which issues belong to which file and makes the output difficult to interpret.
This issue occurs regardless of output format (both --format table and --format json produce the same problem), suggesting it's a core issue with the Azure ARM scanner logic rather than a formatting problem.
Desired Behavior
When scanning a single Azure ARM template file, all scan results should appear under one section with the correct target filename. The output should show:
Only one section: "dummy-arm-v1.0.json (azure-arm)"
All detected issues (misconfigurations, vulnerabilities, etc.) grouped together under this single target
No empty or unnamed target sections
Actual Behavior
When scanning a single Azure ARM template, the results are incorrectly split into two sections:
First section: " (azure-arm)" (empty target name) - contains some scan results
Second section: "owldb-arm-v1.0.json (azure-arm)" (correct filename) - contains other scan results
In table format, this also manifests as an empty Target field in the summary table, making it unclear which results belong to which file.
Reproduction Steps
1. Create any Azure ARM template file (e.g., dummy-arm-v1.0.json) { "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": { "storageAccountName": { "type": "string", "defaultValue": "dummystorage123", "metadata": { "description": "Name of the storage account" } }, "location": { "type": "string", "defaultValue": "[resourceGroup().location]", "metadata": { "description": "Location for all resources" } } }, "variables": { "storageAccountName": "[concat('dummy', uniqueString(resourceGroup().id))]" }, "resources": [ { "type": "Microsoft.Storage/storageAccounts", "apiVersion": "2024-01-01", "name": "[variables('storageAccountName')]", "location": "[parameters('location')]", "sku": { "name": "Standard_LRS" }, "kind": "StorageV2", "properties": { "accessTier": "Hot", "allowBlobPublicAccess": true, "supportsHttpsTrafficOnly": false, "minimumTlsVersion": "TLS1_0" } }, { "type": "Microsoft.Storage/storageAccounts/blobServices", "apiVersion": "2024-01-01", "name": "[concat(variables('storageAccountName'), '/default')]", "dependsOn": [ "[resourceId('Microsoft.Storage/storageAccounts', variables('storageAccountName'))]" ], "properties": { "deleteRetentionPolicy": { "enabled": false } } } ], "outputs": { "storageAccountName": { "type": "string", "value": "[variables('storageAccountName')]" }, "storageAccountId": { "type": "string", "value": "[resourceId('Microsoft.Storage/storageAccounts', variables('storageAccountName'))]" } } }Observe the output - you will see two separate result sections instead of one
The same issue occurs with JSON format:
Operating System
Ubuntu 22.04 LTS
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions