HbaseApplication · Apache
CVE-2019-15544
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 · uneditedAn issue was discovered in the protobuf crate before 2.6.0 for Rust. Attackers can exhaust all memory via Vec::reserve calls.
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 confidenceThe protobuf Rust crate before version 2.6.0 contains a vulnerability where attackers can trigger excessive memory allocation through Vec::reserve calls, leading to memory exhaustion and denial of service. This is a classic resource consumption vulnerability in the protobuf parsing logic.
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
HbaseApplication
= 2.2.3< 1.7.5>= 2.0.0, < 2.6.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Check if Apache HBase 2.2.3 is installedRun 'hbase version' or check the running HBase process versionAffected if The version reported is exactly 2.2.3
-
Check Cargo.lock for protobuf crate versionSearch for 'name = "protobuf"' in Cargo.lock and note the version fieldAffected if The version is less than 1.7.5, or greater than or equal to 2.0.0 but less than 2.6.0
-
Check Cargo.toml direct dependenciesInspect the dependencies section of Cargo.toml for a 'protobuf' entryAffected if A protobuf dependency specifies a version matching the vulnerable ranges (such as '2.5.0' or '1.0.0')
-
Determine if protobuf parsing is in useSearch code for imports of protobuf-generated structs or calls to protobuf parsing functions (parse_from_bytes, merge_from, etc.)Affected if The application parses protobuf messages from external or untrusted sources using the vulnerable crate version
A user is affected if they run Apache HBase 2.2.3 or have the Rust protobuf crate at version 1.7.5 or below, or between 2.0.0 and 2.6.0, and parse untrusted protobuf data.
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.
From vendor data1.7.52.6.0
Upgrade the protobuf crate to version 2.6.0 or later in Cargo.toml and verify the application compiles and functions correctly with the updated dependency.
Fix this in Hbase
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15544 — 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-2019-15544 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