보안 업데이트가 누락된 티켓팅 시스템의 원격 Red Hat 호스트와 관련된 취약점이 수정되었습니다.
플랫폼 인증:
새로 생성된 조직이 서버 데이터 IP에 연결할 수 없습니다. 모든 cplb-init 및 storage-ipsec-config-bm-XXXXX 작업에 Failed to connect to the host via ssh: ssh: connect to host 10.1.18.X port 22: Connection timed out 메시지가 표시됩니다.
업그레이드:
1.9.12에서 1.9.13으로 업그레이드하는 동안 atat-webhooks 부가기능에서 업그레이드가 실패합니다.
1.9.12에서 1.9.13으로 업그레이드하는 동안 테넌트 조직 베어메탈의 노드 OS 업그레이드가 실패합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eGoogle Distributed Cloud air-gapped 1.9.13 has been released, offering new features detailed in the product overview.\u003c/p\u003e\n"],["\u003cp\u003eThe Canonical Ubuntu OS image has been updated to version 20240402, including fixes for numerous security vulnerabilities, which will require upgrading all nodes to benefit from.\u003c/p\u003e\n"],["\u003cp\u003eSecurity improvements have been implemented in the GDC console to enforce strict transport security.\u003c/p\u003e\n"],["\u003cp\u003eA vulnerability regarding missing security updates in the remote Red Hat host for the ticketing system has been resolved.\u003c/p\u003e\n"],["\u003cp\u003eTwo issues, impacting new organizations and the upgrade process, have been identified for platform authentication, and upgrades from 1.9.12 to 1.9.13, respectively.\u003c/p\u003e\n"]]],[],null,["# Google Distributed Cloud air-gapped 1.9.13 release notes\n\n\u003cbr /\u003e\n\nMay 10, 2024\n------------\n\n*** ** * ** ***\n\nGoogle Distributed Cloud air-gapped 1.9.13 is released.\n\nSee the [product overview](/distributed-cloud/hosted/docs/latest/gdch/overview) to learn about the features of Google Distributed Cloud air-gapped.\n\n*** ** * ** ***\n\n\nUpdated Canonical Ubuntu OS image version to 20240402 to apply the latest\nsecurity patches and important updates. To take advantage of the bug and\nsecurity vulnerability fixes, you must upgrade all nodes with each release. The\nfollowing security vulnerabilities are fixed:\n\n- [CVE-2022-28948](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28948)\n- [CVE-2023-0340](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0340)\n- [CVE-2023-1523](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1523)\n- [CVE-2023-4408](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4408)\n- [CVE-2023-4641](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4641)\n- [CVE-2023-5517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-5517)\n- [CVE-2023-6228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-6228)\n- [CVE-2023-6277](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-6277)\n- [CVE-2023-6516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-6516)\n- [CVE-2023-6915](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-6915)\n- [CVE-2023-22995](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22995)\n- [CVE-2023-23000](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23000)\n- [CVE-2023-23004](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23004)\n- [CVE-2023-48733](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48733)\n- [CVE-2023-50387](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-50387)\n- [CVE-2023-50782](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-50782)\n- [CVE-2023-50868](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-50868)\n- [CVE-2023-51779](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-51779)\n- [CVE-2023-51781](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-51781)\n- [CVE-2023-51782](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-51782)\n- [CVE-2023-52356](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52356)\n- [CVE-2024-0565](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-0565)\n- [CVE-2024-0646](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-0646)\n- [CVE-2024-2398](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-2398)\n- [CVE-2024-22667](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-22667)\n- [CVE-2024-24806](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24806)\n- [CVE-2024-24855](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24855)\n- [CVE-2024-28085](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-28085)\n\n*** ** * ** ***\n\n\nFixed vulnerabilities in the GDC console where strict transport\nsecurity was not enforced.\n\n*** ** * ** ***\n\n\nFixed a vulnerability with the remote Red Hat host for the ticketing\nsystem missing security updates.\n\n*** ** * ** ***\n\n**Platform authentication**:\n\n- Newly created orgs can't reach the server data IPs. All `cplb-init` and `storage-ipsec-config-bm-XXXXX` jobs display the follow message: `Failed to connect to the host via ssh: ssh: connect to host 10.1.18.X port 22: Connection timed out`.\n\n**Upgrade**:\n\n- An upgrade fails on `atat-webhooks` add-on while upgrading from 1.9.12 to 1.9.13.\n- The Node OS upgrade on tenant org bare metal fails while upgrading from 1.9.12 to 1.9.13."]]
