Skip to content

Commit c737cd0

Browse files
Fix querying by commit integration test more (#2146)
The additional matching CVE has now been rejected, and the text of the description has changed. I suspect we haven't seen the last of this yet, as a rejected CVE should be resulting in a withdrawn OSV record... (I'm investigating why that isn't the case, but want to unbreak the test)
1 parent aad1acb commit c737cd0

File tree

1 file changed

+5
-13
lines changed

1 file changed

+5
-13
lines changed

gcp/api/integration_tests.py

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -97,21 +97,13 @@ class IntegrationTests(unittest.TestCase,
9797

9898
_VULN_31745 = {
9999
'id': 'CVE-2024-31745',
100-
'details':
101-
('Libdwarf v0.9.1 was discovered to contain a heap use-after-free '
102-
'via the dw_empty_errlist_item function at /libdwarf/dwarf_alloc.c.'
103-
),
100+
'details': ('Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. '
101+
'ConsultIDs: CVE-2024-2002. Reason: This candidate is a '
102+
'duplicate of CVE-2024-2002. Notes: All CVE users '
103+
'should reference CVE-2024-2002 instead of this '
104+
'candidate.'),
104105
'modified': '2024-04-20T01:04:38.640360Z',
105106
'published': '2024-04-19T13:15:13Z',
106-
'references': [{
107-
'type':
108-
'FIX',
109-
'url': ('https://github.com/davea42/libdwarf-code/commit/'
110-
'404e6b1b14f60c81388d50b4239f81d461b3c3ad')
111-
}, {
112-
'type': 'REPORT',
113-
'url': 'https://github.com/davea42/libdwarf-code/issues/238'
114-
}],
115107
'affected': [{
116108
'ranges': [{
117109
'type':

0 commit comments

Comments
 (0)