登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
登录
注册
9月20日,Gitee × 模力方舟来成都了!聚焦 AI 应用在开发范式、算力架构、交互设计、硬件选型等跨场景创新实践,点击立即报名~
代码拉取完成,页面将自动刷新
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
12
Star
0
Fork
16
src-openEuler
/
cri-tools
代码
Issues
22
Pull Requests
2
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
我知道了,不再自动展开
更新失败,请稍后重试!
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息,仓库外成员不可访问
CVE-2024-29018
待办的
#I9AWLZ
CVE和安全问题
openeuler-ci-bot
拥有者
创建于
2024-03-23 08:49
一、漏洞信息 漏洞编号:[CVE-2024-29018](https://nvd.nist.gov/vuln/detail/CVE-2024-29018) 漏洞归属组件:[cri-tools](https://gitee.com/src-openeuler/cri-tools) 漏洞归属的版本:1.22.0,1.24.2 CVSS V3.0分值: BaseScore:7.5 High Vector:CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N 漏洞简述: Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby s networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well.When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly.In addition to configuring the Linux kernel s various networking features to enable container networking, `dockerd` directly provides some services to container networks. Principal among these is serving as a resolver, enabling service discovery, and resolution of names from an upstream resolver.When a DNS request for a name that does not correspond to a container is received, the request is forwarded to the configured upstream resolver. This request is made from the container s network namespace: the level of access and routing of traffic is the same as if the request was made by the container itself.As a consequence of this design, containers solely attached to an internal network will be unable to resolve names using the upstream resolver, as the container itself is unable to communicate with that nameserver. Only the names of containers also attached to the internal network are able to be resolved.Many systems run a local forwarding DNS resolver. As the host and any containers have separate loopback devices, a consequence of the design described above is that containers are unable to resolve names from the host s configured resolver, as they cannot reach these addresses on the host loopback device. To bridge this gap, and to allow containers to properly resolve names even when a local forwarding resolver is used on a loopback address, `dockerd` detects this scenario and instead forward DNS requests from the host namework namespace. The loopback resolver then forwards the requests to its configured upstream resolvers, as expected.Because `dockerd` forwards DNS requests to the host loopback device, bypassing the container network namespace s normal routing semantics entirely, internal networks can unexpectedly forward DNS requests to an external nameserver. By registering a domain for which they control the authoritative nameservers, an attacker could arrange for a compromised container to exfiltrate data by encoding it in DNS queries that will eventually be answered by their nameservers.Docker Desktop is not affected, as Docker Desktop always runs an internal resolver on a RFC 1918 address.Moby releases 26.0.0, 25.0.4, and 23.0.11 are patched to prevent forwarding any DNS requests from internal networks. As a workaround, run containers intended to be solely attached to internal networks with a custom upstream address, which will force all upstream DNS queries to be resolved from the container s network namespace. 漏洞公开时间:2024-03-21 05:15:31 漏洞创建时间:2024-03-23 00:49:52 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2024-29018 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | security-advisories.github.com | https://github.com/moby/moby/pull/46609 | | | security-advisories.github.com | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | | | af854a3a-2127-422b-91ae-364da2661108 | https://github.com/moby/moby/pull/46609 | | | af854a3a-2127-422b-91ae-364da2661108 | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-29018 | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-29018 | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://github.com/moby/moby/pull/46609 | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2270591 | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://github.com/CVEProject/cvelistV5/blob/main//cves/2024/29xxx/CVE-2024-29018.json | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | redhat_bugzilla | https://github.com/moby/moby/pull/46609 | https://bugzilla.redhat.com/show_bug.cgi?id=2270591 | | redhat_bugzilla | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | https://bugzilla.redhat.com/show_bug.cgi?id=2270591 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:7164 | https://bugzilla.redhat.com/show_bug.cgi?id=2270591 | | debian | | https://security-tracker.debian.org/tracker/CVE-2024-29018 | | cve_search | | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | | cve_search | | https://github.com/moby/moby/pull/46609 | | github_advisory | https://github.com/moby/moby/pull/46609 | https://github.com/advisories/GHSA-mq39-4gv4-mvpx | | github_advisory | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | https://github.com/advisories/GHSA-mq39-4gv4-mvpx | | go | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | https://github.com/golang/vulndb/blob/master/reports/GO-2024-2659.yaml | | go | https://github.com/moby/moby/pull/46609 | https://github.com/golang/vulndb/blob/master/reports/GO-2024-2659.yaml | | amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2024-29018 | https://explore.alas.aws.amazon.com/CVE-2024-29018.html | | amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29018 | https://explore.alas.aws.amazon.com/CVE-2024-29018.html | | snyk | https://github.com/moby/moby/commit/790c3039d0ca5ed86ecd099b4b571496607628bc | https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDOCKERDOCKERLIBNETWORK-6474507 | | snyk | https://github.com/moby/moby/commit/a987bc5ad06c54448454b5415dd70465d41c184e | https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDOCKERDOCKERLIBNETWORK-6474507 | | snyk | https://github.com/moby/moby/pull/46609 | https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDOCKERDOCKERLIBNETWORK-6474507 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | | | https://github.com/moby/moby/pull/46609 | | security-advisories.github.com | | | | https://github.com/moby/moby/pull/46609 | | af854a3a-2127-422b-91ae-364da2661108 | | | | https://github.com/moby/moby/pull/46609 | | suse_bugzilla | | | | https://github.com/moby/moby/pull/46609 | | redhat_bugzilla | | | | https://github.com/moby/moby/pull/46609 | | github_advisory | | | | https://github.com/moby/moby/pull/46609 | | go | | | | https://github.com/moby/moby/commit/790c3039d0ca5ed86ecd099b4b571496607628bc | | snyk | | | | https://github.com/moby/moby/commit/a987bc5ad06c54448454b5415dd70465d41c184e | | snyk | | | | https://github.com/moby/moby/pull/46609 | | snyk | | | | https://github.com/moby/moby/pull/46609 | | nvd | | | | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | | nvd | </details> 二、漏洞分析结构反馈 影响性分析说明: openEuler评分: 5.9 Vector:CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N 受影响版本排查(受影响/不受影响): 1.master(1.29.0): 2.openEuler-20.03-LTS-SP1: 3.openEuler-20.03-LTS-SP4: 4.openEuler-22.03-LTS(1.22.0): 5.openEuler-22.03-LTS-Next(1.22.0): 6.openEuler-22.03-LTS-SP1(1.22.0): 7.openEuler-22.03-LTS-SP2(1.22.0): 8.openEuler-22.03-LTS-SP3(1.22.0): 9.openEuler-24.03-LTS(1.29.0): 10.openEuler-22.03-LTS-SP4(1.22.0): 11.openEuler-24.03-LTS-Next(1.29.0): 12.openEuler-24.03-LTS-SP2(1.29.0): 修复是否涉及abi变化(是/否): 1.master(1.29.0): 2.openEuler-20.03-LTS-SP1: 3.openEuler-20.03-LTS-SP4: 4.openEuler-22.03-LTS(1.22.0): 5.openEuler-22.03-LTS-Next(1.22.0): 6.openEuler-22.03-LTS-SP1(1.22.0): 7.openEuler-22.03-LTS-SP2(1.22.0): 8.openEuler-22.03-LTS-SP3(1.22.0): 9.openEuler-24.03-LTS(1.29.0): 10.openEuler-24.03-LTS-SP2(1.29.0): 原因说明: 1.master(1.29.0): 2.openEuler-20.03-LTS-SP4: 3.openEuler-22.03-LTS-SP3(1.22.0): 4.openEuler-22.03-LTS-SP4(1.22.0): 5.openEuler-24.03-LTS(1.29.0): 6.openEuler-24.03-LTS-Next(1.29.0): 7.openEuler-24.03-LTS-SP1(1.29.0): 8.openEuler-24.03-LTS-SP2(1.29.0):
一、漏洞信息 漏洞编号:[CVE-2024-29018](https://nvd.nist.gov/vuln/detail/CVE-2024-29018) 漏洞归属组件:[cri-tools](https://gitee.com/src-openeuler/cri-tools) 漏洞归属的版本:1.22.0,1.24.2 CVSS V3.0分值: BaseScore:7.5 High Vector:CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N 漏洞简述: Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby s networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well.When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly.In addition to configuring the Linux kernel s various networking features to enable container networking, `dockerd` directly provides some services to container networks. Principal among these is serving as a resolver, enabling service discovery, and resolution of names from an upstream resolver.When a DNS request for a name that does not correspond to a container is received, the request is forwarded to the configured upstream resolver. This request is made from the container s network namespace: the level of access and routing of traffic is the same as if the request was made by the container itself.As a consequence of this design, containers solely attached to an internal network will be unable to resolve names using the upstream resolver, as the container itself is unable to communicate with that nameserver. Only the names of containers also attached to the internal network are able to be resolved.Many systems run a local forwarding DNS resolver. As the host and any containers have separate loopback devices, a consequence of the design described above is that containers are unable to resolve names from the host s configured resolver, as they cannot reach these addresses on the host loopback device. To bridge this gap, and to allow containers to properly resolve names even when a local forwarding resolver is used on a loopback address, `dockerd` detects this scenario and instead forward DNS requests from the host namework namespace. The loopback resolver then forwards the requests to its configured upstream resolvers, as expected.Because `dockerd` forwards DNS requests to the host loopback device, bypassing the container network namespace s normal routing semantics entirely, internal networks can unexpectedly forward DNS requests to an external nameserver. By registering a domain for which they control the authoritative nameservers, an attacker could arrange for a compromised container to exfiltrate data by encoding it in DNS queries that will eventually be answered by their nameservers.Docker Desktop is not affected, as Docker Desktop always runs an internal resolver on a RFC 1918 address.Moby releases 26.0.0, 25.0.4, and 23.0.11 are patched to prevent forwarding any DNS requests from internal networks. As a workaround, run containers intended to be solely attached to internal networks with a custom upstream address, which will force all upstream DNS queries to be resolved from the container s network namespace. 漏洞公开时间:2024-03-21 05:15:31 漏洞创建时间:2024-03-23 00:49:52 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2024-29018 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | security-advisories.github.com | https://github.com/moby/moby/pull/46609 | | | security-advisories.github.com | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | | | af854a3a-2127-422b-91ae-364da2661108 | https://github.com/moby/moby/pull/46609 | | | af854a3a-2127-422b-91ae-364da2661108 | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-29018 | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-29018 | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://github.com/moby/moby/pull/46609 | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2270591 | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | suse_bugzilla | https://github.com/CVEProject/cvelistV5/blob/main//cves/2024/29xxx/CVE-2024-29018.json | https://bugzilla.suse.com/show_bug.cgi?id=1234089 | | redhat_bugzilla | https://github.com/moby/moby/pull/46609 | https://bugzilla.redhat.com/show_bug.cgi?id=2270591 | | redhat_bugzilla | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | https://bugzilla.redhat.com/show_bug.cgi?id=2270591 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:7164 | https://bugzilla.redhat.com/show_bug.cgi?id=2270591 | | debian | | https://security-tracker.debian.org/tracker/CVE-2024-29018 | | cve_search | | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | | cve_search | | https://github.com/moby/moby/pull/46609 | | github_advisory | https://github.com/moby/moby/pull/46609 | https://github.com/advisories/GHSA-mq39-4gv4-mvpx | | github_advisory | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | https://github.com/advisories/GHSA-mq39-4gv4-mvpx | | go | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | https://github.com/golang/vulndb/blob/master/reports/GO-2024-2659.yaml | | go | https://github.com/moby/moby/pull/46609 | https://github.com/golang/vulndb/blob/master/reports/GO-2024-2659.yaml | | amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2024-29018 | https://explore.alas.aws.amazon.com/CVE-2024-29018.html | | amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29018 | https://explore.alas.aws.amazon.com/CVE-2024-29018.html | | snyk | https://github.com/moby/moby/commit/790c3039d0ca5ed86ecd099b4b571496607628bc | https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDOCKERDOCKERLIBNETWORK-6474507 | | snyk | https://github.com/moby/moby/commit/a987bc5ad06c54448454b5415dd70465d41c184e | https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDOCKERDOCKERLIBNETWORK-6474507 | | snyk | https://github.com/moby/moby/pull/46609 | https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDOCKERDOCKERLIBNETWORK-6474507 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | | | https://github.com/moby/moby/pull/46609 | | security-advisories.github.com | | | | https://github.com/moby/moby/pull/46609 | | af854a3a-2127-422b-91ae-364da2661108 | | | | https://github.com/moby/moby/pull/46609 | | suse_bugzilla | | | | https://github.com/moby/moby/pull/46609 | | redhat_bugzilla | | | | https://github.com/moby/moby/pull/46609 | | github_advisory | | | | https://github.com/moby/moby/pull/46609 | | go | | | | https://github.com/moby/moby/commit/790c3039d0ca5ed86ecd099b4b571496607628bc | | snyk | | | | https://github.com/moby/moby/commit/a987bc5ad06c54448454b5415dd70465d41c184e | | snyk | | | | https://github.com/moby/moby/pull/46609 | | snyk | | | | https://github.com/moby/moby/pull/46609 | | nvd | | | | https://github.com/moby/moby/security/advisories/GHSA-mq39-4gv4-mvpx | | nvd | </details> 二、漏洞分析结构反馈 影响性分析说明: openEuler评分: 5.9 Vector:CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N 受影响版本排查(受影响/不受影响): 1.master(1.29.0): 2.openEuler-20.03-LTS-SP1: 3.openEuler-20.03-LTS-SP4: 4.openEuler-22.03-LTS(1.22.0): 5.openEuler-22.03-LTS-Next(1.22.0): 6.openEuler-22.03-LTS-SP1(1.22.0): 7.openEuler-22.03-LTS-SP2(1.22.0): 8.openEuler-22.03-LTS-SP3(1.22.0): 9.openEuler-24.03-LTS(1.29.0): 10.openEuler-22.03-LTS-SP4(1.22.0): 11.openEuler-24.03-LTS-Next(1.29.0): 12.openEuler-24.03-LTS-SP2(1.29.0): 修复是否涉及abi变化(是/否): 1.master(1.29.0): 2.openEuler-20.03-LTS-SP1: 3.openEuler-20.03-LTS-SP4: 4.openEuler-22.03-LTS(1.22.0): 5.openEuler-22.03-LTS-Next(1.22.0): 6.openEuler-22.03-LTS-SP1(1.22.0): 7.openEuler-22.03-LTS-SP2(1.22.0): 8.openEuler-22.03-LTS-SP3(1.22.0): 9.openEuler-24.03-LTS(1.29.0): 10.openEuler-24.03-LTS-SP2(1.29.0): 原因说明: 1.master(1.29.0): 2.openEuler-20.03-LTS-SP4: 3.openEuler-22.03-LTS-SP3(1.22.0): 4.openEuler-22.03-LTS-SP4(1.22.0): 5.openEuler-24.03-LTS(1.29.0): 6.openEuler-24.03-LTS-Next(1.29.0): 7.openEuler-24.03-LTS-SP1(1.29.0): 8.openEuler-24.03-LTS-SP2(1.29.0):
评论 (
3
)
登录
后才可以发表评论
状态
待办的
待办的
已挂起
进行中
已完成
已拒绝
负责人
未设置
xuxuepeng
xuxuepeng
负责人
协作者
+负责人
+协作者
标签
CVE/UNFIXED
sig/sig-CloudNative
未设置
项目
未立项任务
未立项任务
里程碑
未关联里程碑
未关联里程碑
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (18)
标签 (11)
master
openEuler-24.03-LTS-Next
openEuler-24.03-LTS-SP2
openEuler-24.03-LTS-SP1
openEuler-24.03-LTS
openEuler-24.09
openEuler-25.03
openEuler-25.09
openEuler-22.03-LTS-SP3
openEuler-22.03-LTS-SP2
openEuler-22.03-LTS-SP1
openEuler-22.03-LTS-Next
openEuler-22.03-LTS-SP4
openEuler-23.09
openEuler-22.03-LTS
openEuler-22.09
openEuler-23.03
openEuler-20.09
openEuler-24.03-LTS-SP2-release
openEuler-24.03-LTS-SP1-release
openEuler-22.03-LTS-SP4-release
openEuler-24.09-release
openEuler-24.03-LTS-release
openEuler-22.03-LTS-SP3-release
openEuler-23.09-rc5
openEuler-22.03-LTS-SP1-release
openEuler-22.09-release
openEuler-22.09-rc5
openEuler-22.09-20220829
开始日期   -   截止日期
-
置顶选项
不置顶
置顶等级:高
置顶等级:中
置顶等级:低
优先级
不指定
严重
主要
次要
不重要
预计工期
(小时)
参与者(1)
1
https://gitee.com/src-openeuler/cri-tools.git
git@gitee.com:src-openeuler/cri-tools.git
src-openeuler
cri-tools
cri-tools
点此查找更多帮助
搜索帮助
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号,请先登录后再操作。
立即登录
没有帐号,去注册