How severe is CVE-2023-44313?

CVE-2023-44313 has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-44313?

CVE-2023-44313 affects the following packages: github.com/apache/servicecomb-service-center (Go). Ecosystems affected: Go.

How do I fix CVE-2023-44313?

Update github.com/apache/servicecomb-service-center to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-44313 is resolved across your whole dependency graph.

How do I detect CVE-2023-44313 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apache/servicecomb-service-center, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-44313 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2023-44313 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-44313 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-44313?

CVE-2023-44313 has an EPSS (Exploit Prediction Scoring System) score of 3.5%, placing it in the 89th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-44313?

CVE-2023-44313 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2023-44313 published, and has it been updated?

CVE-2023-44313 was published on January 31, 2024 and was last updated on February 13, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2023-44313 — servicecomb-service-center

HIGH

CVE-2023-44313 is a high-severity (CVSS 7.6) Server-Side Request Forgery (SSRF) vulnerability in github.com/apache/servicecomb-service-center. A fix is available for github.com/apache/servicecomb-service-center — see the affected versions and patch details below.

Apache ServiceComb Service-Center Server-Side Request Forgery vulnerability

Also known asGO-2024-2495

Published

Jan 31, 2024

Updated

Feb 13, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-44313.

EPSS Exploitation Probability

via FIRST.org ↗

3.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/apache/servicecomb-service-center

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Server-Side Request Forgery (SSRF) vulnerability in Apache ServiceComb Service-Center. Attackers can obtain sensitive server information through specially crafted requests.This issue affects Apache ServiceComb before 2.1.0 (included). Users are recommended to upgrade to version 2.2.0, which fixes the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/apache/servicecomb-service-center`	all versions	2.2.0`go get github.com/apache/servicecomb-service-center@v2.2.0`

Affected Products

1 product · 1 configurations

Application

servicecombapache

< 2.2.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apache/servicecomb-service-center, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/apache/servicecomb-service-center to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-44313 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-44313 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.6/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

Low

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

servicecomb-service-center

3.6/10

Code-Review5/10

Maintained0/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Jan 31, 2024

Last updated

Feb 13, 2025

Identifiers

CVE-2023-44313

GO-2024-2495

References

Advisorynvd.nist.gov · CVE 2023 44313 Weblists.apache.org · kxovd455o9h4f2v811hcov2qknbwld5r Webopenwall.com Packagegithub.com · servicecomb service center

Related vulnerabilities

Also affects servicecomb-service-center

This CVE is high severity; 1 of 2 other CVEs affecting servicecomb-service-center is rated as high or higher (top: high).

CVE-2023-44312CVE-2021-21501

Same weakness: CWE-918

This CVE is high severity — higher than any of the other 6 CVEs with CWE-918 (highest there: moderate).

CVE-2026-126062CVE-2026-79914CVE-2026-88983CVE-2026-28385GHSA-7wpf-ch8f-5f4xCVE-2026-54442Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 13, 2025