Skip to content
Fencer Intel
high 7.5

CVE-2020-1925 json

Server-Side Request Forgery (SSRF) in Apache Olingo

published 2020-01-09 6 y ago modified 2026-06-17 4 mo ago also GHSA-v4qh-6367-4cx2 , EUVD-2020-0315

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

Apache Olingo versions 4.0.0 to 4.7.0 provide the AsyncRequestWrapperImpl class which reads a URL from the Location header, and then sends a GET or DELETE request to this URL. It may allow to implement a SSRF attack. If an attacker tricks a client to connect to a malicious server, the server can make the client call any URL including internal resources which are not directly accessible by the attacker.

Patch / fix

  • maven org.apache.olingo:odata-client-core 4.7.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-1925 updated cvss 6.8

olingo-odata: Server side request forgery in AsyncResponseWrapperImpl

  • Red Hat JBoss Data Virtualization 6 teiid-olingo teiid-olingo, teiid-olingo-odata4 teiid-olingo-odata4
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 7.9
    fixed: vendor fix RHSA-2021:3140

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.83% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.olingo:odata-client-core
>=4.0.0, <4.7.1
4.7.1

Affected products

  • Apache Software Foundation Apache Olingo

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.