OlingoApplication · Apache
CVE-2019-17555
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 · uneditedThe AsyncResponseWrapperImpl class in Apache Olingo versions 4.0.0 to 4.6.0 reads the Retry-After header and passes it to the Thread.sleep() method without any check. If a malicious server returns a huge value in the header, then it can help to implement a DoS attack.
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 AsyncResponseWrapperImpl class in Apache Olingo 4.0.0-4.6.0 reads the Retry-After HTTP header from server responses and passes the value directly to Thread.sleep() without any validation or bounds checking. A malicious server can return an extremely large header value, causing the client thread to block for an extended period and resulting in denial of service.
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
OlingoApplication
>= 4.0.0, <= 4.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.
-
Identify Apache Olingo library versionInspect your project's dependency management file (pom.xml, build.gradle, or equivalent) for the Apache Olingo dependency version, or list the olingo-*.jar files in your classpath and check their versioned filenames.Affected if The version listed is between 4.0.0 and 4.6.0 inclusive.
-
Locate the AsyncResponseWrapperImpl class in the classpathSearch your deployed application libraries for a JAR file containing 'olingo' in the name and verify it includes the class 'org.apache.olingo.client.core.AsyncResponseWrapperImpl' or similar path containing 'AsyncResponseWrapperImpl'.Affected if This class exists in your runtime libraries and the version from step 1 is in the affected range.
-
Determine if your application uses OData client operationsReview application code for usage of ODataClient or related client classes (such as AsyncClient or DefaultODataClient) that perform HTTP requests to OData services.Affected if Your code uses Olingo client APIs to make outbound HTTP requests to OData services.
-
Assess trust boundary of OData service endpointsIdentify all OData service URLs your application connects to and determine whether they are trusted internal services or external/untrusted endpoints.Affected if Your application makes client requests to external or untrusted OData servers that could return malicious HTTP headers.
You are affected if your application uses Apache Olingo versions 4.0.0-4.6.0 and acts as an HTTP client connecting to OData services where a malicious server could supply an arbitrarily large Retry-After header value.
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 dataUpgrade to Apache Olingo version 4.7.0 or later which implements proper validation of the Retry-After header value before passing it to Thread.sleep().
Fix this in Olingo
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17555 — 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-17555 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