Skip to content

Commit a478e4b

Browse files
osv-robotosv-robot
authored
test: update apitester snapshots (#4980)
The snapshots have changed, probably due to OSV advisories being changed. Please review the differences to make sure that they're expected!
1 parent 1f963c5 commit a478e4b

2 files changed

Lines changed: 28 additions & 36 deletions

File tree

‎tools/apitester/__snapshots__/cassette_TestCommand_JavareachArchive.snap‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,10 @@
1717
{},
1818
{
1919
"vulns": [
20+
{
21+
"id": "GHSA-72hv-8253-57qq",
22+
"modified": "<RFC3339 date with the year 2026>"
23+
},
2024
{
2125
"id": "GHSA-h46c-h94j-95f3",
2226
"modified": "<RFC3339 date with the year 2026>"
@@ -254,6 +258,10 @@
254258
{
255259
"id": "GHSA-qh8g-58pp-2wxh",
256260
"modified": "<RFC3339 date with the year 2026>"
261+
},
262+
{
263+
"id": "GHSA-wjpw-4j6x-6rwh",
264+
"modified": "<RFC3339 date with the year 2026>"
257265
}
258266
]
259267
},
@@ -306,6 +314,10 @@
306314
{},
307315
{
308316
"vulns": [
317+
{
318+
"id": "GHSA-72hv-8253-57qq",
319+
"modified": "<RFC3339 date with the year 2026>"
320+
},
309321
{
310322
"id": "GHSA-h46c-h94j-95f3",
311323
"modified": "<RFC3339 date with the year 2026>"
@@ -543,6 +555,10 @@
543555
{
544556
"id": "GHSA-qh8g-58pp-2wxh",
545557
"modified": "<RFC3339 date with the year 2026>"
558+
},
559+
{
560+
"id": "GHSA-wjpw-4j6x-6rwh",
561+
"modified": "<RFC3339 date with the year 2026>"
546562
}
547563
]
548564
},

‎tools/apitester/__snapshots__/cassette_single_query.snap‎

Lines changed: 12 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -1029,7 +1029,7 @@
10291029
"id": "CURL-CVE-2024-9681",
10301030
"summary": "HSTS subdomain overwrites parent cache entry",
10311031
"details": "When curl is asked to use HSTS, the expiry time for a subdomain might\noverwrite a parent domain's cache entry, making it end sooner or later than\notherwise intended.\n\nThis affects curl using applications that enable HSTS and use URLs with the\ninsecure `HTTP://` scheme and perform transfers with hosts like\n`x.example.com` as well as `example.com` where the first host is a subdomain\nof the second host.\n\n(The HSTS cache either needs to have been populated manually or there needs to\nhave been previous HTTPS accesses done as the cache needs to have entries for\nthe domains involved to trigger this problem.)\n\nWhen `x.example.com` responds with `Strict-Transport-Security:` headers, this\nbug can make the subdomain's expiry timeout *bleed over* and get set for the\nparent domain `example.com` in curl's HSTS cache.\n\nThe result of a triggered bug is that HTTP accesses to `example.com` get\nconverted to HTTPS for a different period of time than what was asked for by\nthe origin server. If `example.com` for example stops supporting HTTPS at its\nexpiry time, curl might then fail to access `http://example.com` until the\n(wrongly set) timeout expires. This bug can also expire the parent's entry\n*earlier*, thus making curl inadvertently switch back to insecure HTTP earlier\nthan otherwise intended.",
1032-
"aliases": ["CVE-2024-9681", "ROOT-OS-DEBIAN-11-CVE-2024-9681"],
1032+
"aliases": ["CVE-2024-9681"],
10331033
"modified": "<RFC3339 date with the year 2026>",
10341034
"published": "2024-11-05T08:00:00Z",
10351035
"database_specific": "<Any value>",
@@ -2299,7 +2299,7 @@
22992299
{
23002300
"id": "CVE-2024-9681",
23012301
"details": "When curl is asked to use HSTS, the expiry time for a subdomain might\noverwrite a parent domain's cache entry, making it end sooner or later than\notherwise intended.\n\nThis affects curl using applications that enable HSTS and use URLs with the\ninsecure `HTTP://` scheme and perform transfers with hosts like\n`x.example.com` as well as `example.com` where the first host is a subdomain\nof the second host.\n\n(The HSTS cache either needs to have been populated manually or there needs to\nhave been previous HTTPS accesses done as the cache needs to have entries for\nthe domains involved to trigger this problem.)\n\nWhen `x.example.com` responds with `Strict-Transport-Security:` headers, this\nbug can make the subdomain's expiry timeout *bleed over* and get set for the\nparent domain `example.com` in curl's HSTS cache.\n\nThe result of a triggered bug is that HTTP accesses to `example.com` get\nconverted to HTTPS for a different period of time than what was asked for by\nthe origin server. If `example.com` for example stops supporting HTTPS at its\nexpiry time, curl might then fail to access `http://example.com` until the\n(wrongly set) timeout expires. This bug can also expire the parent's entry\n*earlier*, thus making curl inadvertently switch back to insecure HTTP earlier\nthan otherwise intended.",
2302-
"aliases": ["CURL-CVE-2024-9681", "ROOT-OS-DEBIAN-11-CVE-2024-9681"],
2302+
"aliases": ["CURL-CVE-2024-9681"],
23032303
"modified": "<RFC3339 date with the year 2026>",
23042304
"published": "2024-11-06T08:15:03.740Z",
23052305
"related": [
@@ -2314,64 +2314,44 @@
23142314
"references": [
23152315
{
23162316
"type": "WEB",
2317-
"url": "http://seclists.org/fulldisclosure/2025/Apr/10"
2317+
"url": "http://seclists.org/fulldisclosure/2025/Apr/12"
23182318
},
23192319
{
23202320
"type": "WEB",
2321-
"url": "http://seclists.org/fulldisclosure/2025/Apr/11"
2321+
"url": "http://seclists.org/fulldisclosure/2025/Apr/4"
23222322
},
23232323
{
23242324
"type": "WEB",
2325-
"url": "http://seclists.org/fulldisclosure/2025/Apr/12"
2325+
"url": "http://seclists.org/fulldisclosure/2025/Apr/5"
23262326
},
23272327
{
23282328
"type": "WEB",
2329-
"url": "http://seclists.org/fulldisclosure/2025/Apr/13"
2329+
"url": "http://seclists.org/fulldisclosure/2025/Apr/9"
23302330
},
23312331
{
23322332
"type": "WEB",
2333-
"url": "http://seclists.org/fulldisclosure/2025/Apr/4"
2333+
"url": "http://seclists.org/fulldisclosure/2025/Apr/10"
23342334
},
23352335
{
23362336
"type": "WEB",
2337-
"url": "http://seclists.org/fulldisclosure/2025/Apr/5"
2337+
"url": "http://seclists.org/fulldisclosure/2025/Apr/11"
23382338
},
23392339
{
23402340
"type": "WEB",
2341-
"url": "http://seclists.org/fulldisclosure/2025/Apr/8"
2341+
"url": "http://seclists.org/fulldisclosure/2025/Apr/13"
23422342
},
23432343
{
23442344
"type": "WEB",
2345-
"url": "http://seclists.org/fulldisclosure/2025/Apr/9"
2346-
},
2347-
{
2348-
"type": "ADVISORY",
2349-
"url": "https://curl.se/docs/CVE-2024-9681.html"
2345+
"url": "http://seclists.org/fulldisclosure/2025/Apr/8"
23502346
},
23512347
{
23522348
"type": "ADVISORY",
23532349
"url": "https://curl.se/docs/CVE-2024-9681.json"
23542350
},
2355-
{
2356-
"type": "ADVISORY",
2357-
"url": "https://hackerone.com/reports/2764830"
2358-
},
2359-
{
2360-
"type": "ADVISORY",
2361-
"url": "http://www.openwall.com/lists/oss-security/2024/11/06/2"
2362-
},
23632351
{
23642352
"type": "ADVISORY",
23652353
"url": "https://security.netapp.com/advisory/ntap-20241213-0006/"
23662354
},
2367-
{
2368-
"type": "REPORT",
2369-
"url": "https://hackerone.com/reports/2764830"
2370-
},
2371-
{
2372-
"type": "FIX",
2373-
"url": "https://curl.se/docs/CVE-2024-9681.html"
2374-
},
23752355
{
23762356
"type": "FIX",
23772357
"url": "https://hackerone.com/reports/2764830"
@@ -2381,12 +2361,8 @@
23812361
"url": "http://www.openwall.com/lists/oss-security/2024/11/06/2"
23822362
},
23832363
{
2384-
"type": "ARTICLE",
2385-
"url": "http://www.openwall.com/lists/oss-security/2024/11/06/2"
2386-
},
2387-
{
2388-
"type": "EVIDENCE",
2389-
"url": "https://hackerone.com/reports/2764830"
2364+
"type": "FIX",
2365+
"url": "https://curl.se/docs/CVE-2024-9681.html"
23902366
}
23912367
],
23922368
"affected": [

0 commit comments

Comments
 (0)