Skip to content

Commit 8d54ac0

Browse files
committed
Fix a CI docs validation error
Signed-off-by: ziad hany <ziadhany2016@gmail.com>
1 parent df9b0fd commit 8d54ac0

1 file changed

Lines changed: 39 additions & 28 deletions

File tree

docs/source/extra-mitigation-curation.rst

Lines changed: 39 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -14,39 +14,50 @@ Follow these steps to provide mitigation information for these advisories.
1414

1515
2. Enter the appropriate mitigation types and mitigation data.
1616

17-
- For each package, provide the mitigation data and notes for the following mitigation types:
18-
19-
- **Upgrade to Versions**: Specify the version(s) users should upgrade to in order
20-
to remediate the vulnerability. Enter one or more fixed versions separated
21-
by commas (e.g., 1.0.1, 2.3.4).
22-
Use the note field for any additional upgrade guidance or constraints.
23-
24-
- **Downgrade to Versions**: Specify the version(s) users should downgrade to if no
25-
fixed upgrade is available. Enter one or more non-vulnerable versions separated
26-
by commas (e.g., 1.0.1, 2.3.4).
27-
Use the note field for any additional guidance or cautions related to the downgrade.
28-
29-
- **Apply Patch**: Provide a URL to the official patch or hotfix that remediates the vulnerability.
30-
Use the note field to include any additional instructions, prerequisites, or known limitations.
31-
32-
- **Change Config**: Provide the configuration changes that mitigate the vulnerability,
33-
such as modifying settings, disabling features, or enabling security controls.
34-
Use the note field to include any potential side effects or additional implementation guidance.
35-
36-
- **Apply Network Restrictions**: Specify the network restrictions required to mitigate
37-
the vulnerability, such as blocking or limiting access to specific ports, IP addresses,
38-
or network ranges. Use the note field to provide firewall rules, scope details, or
39-
additional implementation guidance.
40-
41-
- **Replace Package**: Specify the Package URL of the replacement package to use
42-
instead of the vulnerable package. Use the note field for compatibility
17+
- For each package, provide the mitigation data and
18+
notes for the following mitigation types:
19+
20+
- **Upgrade to Versions**: Specify the version(s) users
21+
should upgrade to in order to remediate the vulnerability.
22+
Enter one or more fixed versions separated by commas
23+
(e.g., 1.0.1, 2.3.4). Use the note field for any
24+
additional upgrade guidance or constraints.
25+
26+
- **Downgrade to Versions**: Specify the version(s) users
27+
should downgrade to if no fixed upgrade is available.
28+
Enter one or more non-vulnerable versions separated
29+
by commas (e.g., 1.0.1, 2.3.4). Use the note field for
30+
any additional guidance or cautions related to the downgrade.
31+
32+
- **Apply Patch**: Provide a URL to the official
33+
patch or hotfix that remediates the vulnerability.
34+
Use the note field to include any additional
35+
instructions, prerequisites, or known limitations.
36+
37+
- **Change Config**: Provide the configuration changes
38+
that mitigate the vulnerability, such as modifying
39+
settings, disabling features, or enabling security controls.
40+
Use the note field to include any potential side effects
41+
or additional implementation guidance.
42+
43+
- **Apply Network Restrictions**: Specify the network
44+
restrictions required to mitigate the vulnerability,
45+
such as blocking or limiting access to specific ports,
46+
IP addresses, or network ranges. Use the note field
47+
to provide firewall rules, scope details, or additional
48+
implementation guidance.
49+
50+
- **Replace Package**: Specify the Package URL of the
51+
replacement package to use instead of the vulnerable
52+
package. Use the note field for compatibility
4353
details or additional guidance.
4454

4555
3. Click **Next item**. If the button is available,
4656
repeat steps 2–3 for each remaining package in the queue.
4757

4858
.. image:: images/extra_mitigation_next_item.png
4959

50-
4. After reviewing all mitigated packages, click **Submit** to save and complete the mitigation curation.
60+
4. After reviewing all mitigated packages,
61+
click **Submit** to save and complete the mitigation curation.
5162

52-
.. image:: images/extra_mitigation_submit.png
63+
.. image:: images/extra_mitigation_submit.png

0 commit comments

Comments
 (0)