BrpcApplication · Apache
CVE-2023-45757
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSecurity vulnerability in Apache bRPC <=1.6.0 on all platforms allows attackers to inject XSS code to the builtin rpcz page. An attacker that can send http request to bRPC server with rpcz enabled can inject arbitrary XSS code to the builtin rpcz page. Solution (choose one of three): 1. upgrade to bRPC > 1.6.0, download link: https://dist.apache.org/repos/dist/release/brpc/1.6.1/ 2. If you are using an old version of bRPC and hard to upgrade, you can apply this patch: https://github.com/apache/brpc/pull/2411 3. disable rpcz feature
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting (XSS) vulnerability in Apache bRPC versions 1.6.0 and below allows attackers to inject arbitrary JavaScript code into the builtin rpcz (RPC tracing) page via specially crafted HTTP requests when the rpcz feature is enabled.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
BrpcApplication
< 1.6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed bRPC versionRun 'brpc --version' or check the library binary version (often via 'ldd' or file metadata). If built from source, check the version tag in the source directory.Affected if version is 1.6.0 or below (any version less than 1.6.1)
-
Confirm rpcz feature is enabledLocate the bRPC server configuration file or startup script. Look for the flag '--enable_rpcz=true' or 'rpcz_enabled=true' in the server launch parameters or configuration.Affected if rpcz feature is explicitly enabled in the server configuration or startup flags
-
Verify rpcz endpoint is accessibleAttempt to access the rpcz page via HTTP: curl http://<server_address>/rpcz . Check if the page loads and returns tracing data.Affected if the rpcz endpoint responds (indicating the feature is active and exposed)
You are affected if your bRPC version is below 1.6.1 AND the rpcz feature is enabled and accessible on your server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.6.1
Upgrade to bRPC version 1.6.1 or later; alternatively, apply the patch from GitHub PR #2411 or disable the rpcz feature if not required.
bRPC 1.6.1
- Download bRPC version 1.6.1 from the official Apache distribution at https://dist.apache.org/repos/dist/release/brpc/1.6.1/
- Extract the source archive and follow the build instructions for your platform
- Rebuild your application or service that uses the bRPC library with the new version
- Restart the bRPC server to load the updated library
- Verify the rpcz page is accessible and functions correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Brpc
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45757 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data