Skip to content

remove actual_time and estimated_time fields#12712

Merged
Maffooch merged 2 commits into
DefectDojo:devfrom
valentijnscholten:remove-actual-estimated-time
Jun 30, 2025
Merged

remove actual_time and estimated_time fields#12712
Maffooch merged 2 commits into
DefectDojo:devfrom
valentijnscholten:remove-actual-estimated-time

Conversation

@valentijnscholten

@valentijnscholten valentijnscholten commented Jun 27, 2025

Copy link
Copy Markdown
Member

Removes Test fields that aren't used/referenced anywhere:

  • actual_time
  • estimated_time

Fixes #11121

@valentijnscholten valentijnscholten added this to the 2.48.0 milestone Jun 27, 2025
@github-actions github-actions Bot added docker New Migration Adding a new migration file. Take care when merging. unittests labels Jun 27, 2025
@dryrunsecurity

dryrunsecurity Bot commented Jun 27, 2025

Copy link
Copy Markdown

DryRun Security

This pull request contains two findings: a potential information disclosure risk from adding new filter fields that might expose sensitive metadata, and a database migration that removes time-tracking fields which could lead to potential data loss, though neither finding is considered blocking.

Information Disclosure in dojo/filters.py
Vulnerability Information Disclosure
Description Adding 'engagement' and 'version' to filter fields could expose sensitive metadata if these fields contain confidential information. This increases the risk of information leakage through API or filter endpoints by making potentially sensitive fields searchable or filterable.

model = Test
fields = ["id", "title", "test_type", "target_start",
"target_end", "notes", "percent_complete",
"engagement", "version",
"branch_tag", "build_id", "commit_hash",
"api_scan_configuration", "scan_type"]

Potential Data Loss in dojo/db_migrations/0232_remove_test_actual_time_remove_test_estimated_time.py
Vulnerability Potential Data Loss
Description Database migration removes 'actual_time' and 'estimated_time' fields from the Test model. If these fields contained critical time-tracking or audit information, their removal could lead to permanent loss of historical data and potentially impact compliance or project tracking capabilities.

# Generated by Django 5.1.8 on 2025-06-27 20:26
from django.db import migrations
class Migration(migrations.Migration):
dependencies = [
('dojo', '0231_alter_finding_cvssv3_alter_finding_template_cvssv3'),
]
operations = [
migrations.RemoveField(
model_name='test',
name='actual_time',
),
migrations.RemoveField(
model_name='test',
name='estimated_time',
),
]


All finding details can be found in the DryRun Security Dashboard.

@mtesauro

Copy link
Copy Markdown
Contributor

Wow, those are some old model fields.

When they were added we were considering tracking the accuracy of estimating manual testing vs the actual time it took the manual test to complete.

As you noticed, that idea was never fully implemented. Thanks for the clean-up work.

@mtesauro mtesauro left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@Maffooch Maffooch requested review from dogboat and hblankenship June 30, 2025 15:05
@Maffooch Maffooch merged commit 84108f6 into DefectDojo:dev Jun 30, 2025
120 of 140 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docker New Migration Adding a new migration file. Take care when merging. unittests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants