Progress DataDirect Connect for JDBC for Amazon Redshift erweiterte Rechte
| CVSS Meta Temp Score | Aktueller Exploitpreis (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Zusammenfassung
In Progress DataDirect Connect for JDBC for Amazon Redshift, DataDirect Connect for JDBC for Apache Cassandra, DataDirect Connect for JDBC for Hive, DataDirect Connect for JDBC for Apache Impala, DataDirect Connect for JDBC for Apache SparkSQL, DataDirect Connect for JDBC Autonomous REST Connector, DataDirect Connect for JDBC for DB2, DataDirect Connect for JDBC for Google Analytics 4, DataDirect Connect for JDBC for Google BigQuery, DataDirect Connect for JDBC for Greenplum, DataDirect Connect for JDBC for Informix, DataDirect Connect for JDBC for Microsoft Dynamics 365, DataDirect Connect for JDBC for Microsoft SQLServer, DataDirect Connect for JDBC for Microsoft Sharepoint, DataDirect Connect for JDBC for MongoDB, DataDirect Connect for JDBC for MySQL, DataDirect Connect for JDBC for Oracle Database, DataDirect Connect for JDBC for Oracle Eloqua, DataDirect Connect for JDBC for Oracle Sales Cloud, DataDirect Connect for JDBC for Oracle Service Cloud, DataDirect Connect for JDBC for PostgreSQL, DataDirect Connect for JDBC for OpenEdge, DataDirect Connect for JDBC for Salesforce, DataDirect Connect for JDBC for SAP HANA, DataDirect Connect for JDBC for SAP S, 4 HANA, DataDirect Connect for JDBC for Sybase ASE, DataDirect Connect for JDBC for Snowflake, DataDirect Hybrid Data Pipeline Server, DataDirect Hybrid Data Pipeline JDBC Driver, DataDirect Hybrid Data Pipeline On Premises Connector, DataDirect Hybrid Data Pipeline Docker and DataDirect OpenAccess JDBC Driver wurde eine kritische Schwachstelle entdeckt. Dabei betrifft es einen unbekannter Codeteil. Dank Manipulation mit unbekannten Daten kann eine erweiterte Rechte-Schwachstelle ausgenutzt werden. Diese Schwachstelle trägt die Bezeichnung CVE-2025-10703. Der Angriff kann über das Netzwerk passieren. Es gibt keinen verfügbaren Exploit. Die Aktualisierung der betroffenen Komponente wird empfohlen.
Details
Eine kritische Schwachstelle wurde in Progress DataDirect Connect for JDBC for Amazon Redshift, DataDirect Connect for JDBC for Apache Cassandra, DataDirect Connect for JDBC for Hive, DataDirect Connect for JDBC for Apache Impala, DataDirect Connect for JDBC for Apache SparkSQL, DataDirect Connect for JDBC Autonomous REST Connector, DataDirect Connect for JDBC for DB2, DataDirect Connect for JDBC for Google Analytics 4, DataDirect Connect for JDBC for Google BigQuery, DataDirect Connect for JDBC for Greenplum, DataDirect Connect for JDBC for Informix, DataDirect Connect for JDBC for Microsoft Dynamics 365, DataDirect Connect for JDBC for Microsoft SQLServer, DataDirect Connect for JDBC for Microsoft Sharepoint, DataDirect Connect for JDBC for MongoDB, DataDirect Connect for JDBC for MySQL, DataDirect Connect for JDBC for Oracle Database, DataDirect Connect for JDBC for Oracle Eloqua, DataDirect Connect for JDBC for Oracle Sales Cloud, DataDirect Connect for JDBC for Oracle Service Cloud, DataDirect Connect for JDBC for PostgreSQL, DataDirect Connect for JDBC for OpenEdge, DataDirect Connect for JDBC for Salesforce, DataDirect Connect for JDBC for SAP HANA, DataDirect Connect for JDBC for SAP S, 4 HANA, DataDirect Connect for JDBC for Sybase ASE, DataDirect Connect for JDBC for Snowflake, DataDirect Hybrid Data Pipeline Server, DataDirect Hybrid Data Pipeline JDBC Driver, DataDirect Hybrid Data Pipeline On Premises Connector, DataDirect Hybrid Data Pipeline Docker sowie DataDirect OpenAccess JDBC Driver entdeckt. Betroffen davon ist ein unbekannter Prozess. Dank der Manipulation mit einer unbekannten Eingabe kann eine erweiterte Rechte-Schwachstelle ausgenutzt werden. Klassifiziert wurde die Schwachstelle durch CWE als CWE-94. Mit Auswirkungen muss man rechnen für Vertraulichkeit, Integrität und Verfügbarkeit. CVE fasst zusammen:
Improper Control of Generation of Code ('Code Injection') vulnerability in Progress DataDirect Connect for JDBC drivers, Progress DataDirect Open Access JDBC driver and Hybrid Data Pipeline allows Remote Code Inclusion.
The SpyAttribute connection option implemented by the DataDirect Connect for JDBC drivers, DataDirect Hybrid Data Pipeline JDBC driver and the DataDirect OpenAccess JDBC driver log=(file) construct allows the user to specify an arbitrary file for the JDBC driver to write its log information to. If an application allows an end user to specify a value for the SpyAttributes connection option then an attacker could cause java script to be written to a log file. If the log file was in the correct location with the correct extension, an application server could see that log file as a resource to be served. The attacker could fetch the resource from the server causing the java script to be executed.
This issue affects:
DataDirect Connect for JDBC for Amazon Redshift: through 6.0.0.001392, fixed in 6.0.0.001541
DataDirect Connect for JDBC for Apache Cassandra: through 6.0.0.000805, fixed in 6.0.0.000833
DataDirect Connect for JDBC for Hive: through 6.0.1.001499, fixed in 6.0.1.001628
DataDirect Connect for JDBC for Apache Impala: through 6.0.0.001155, fixed in 6.0.0.001279
DataDirect Connect for JDBC for Apache SparkSQL: through 6.0.1.001222, fixed in 6.0.1.001344
DataDirect Connect for JDBC Autonomous REST Connector: through 6.0.1.006961, fixed in 6.0.1.007063
DataDirect Connect for JDBC for DB2: through 6.0.0.000717, fixed in 6.0.0.000964
DataDirect Connect for JDBC for Google Analytics 4: through 6.0.0.000454, fixed in 6.0.0.000525
DataDirect Connect for JDBC for Google BigQuery: through 6.0.0.002279, fixed in 6.0.0.002410
DataDirect Connect for JDBC for Greenplum: through 6.0.0.001712, fixed in 6.0.0.001727
DataDirect Connect for JDBC for Informix: through 6.0.0.000690, fixed in 6.0.0.0851
DataDirect Connect for JDBC for Microsoft Dynamics 365: through 6.0.0.003161, fixed in 6.0.0.3198
DataDirect Connect for JDBC for Microsoft SQLServer: through 6.0.0.001936, fixed in 6.0.0.001957
DataDirect Connect for JDBC for Microsoft Sharepoint: through 6.0.0.001559, fixed in 6.0.0.001587
DataDirect Connect for JDBC for MongoDB: through 6.1.0.001654, fixed in 6.1.0.001669
DataDirect Connect for JDBC for MySQL: through 5.1.4.000330, fixed in 5.1.4.000364
DataDirect Connect for JDBC for Oracle Database: through 6.0.0.001747, fixed in 6.0.0.001776
DataDirect Connect for JDBC for Oracle Eloqua: through 6.0.0.001438, fixed in 6.0.0.001458
DataDirect Connect for JDBC for Oracle Sales Cloud: through 6.0.0.001225, fixed in 6.0.0.001316
DataDirect Connect for JDBC for Oracle Service Cloud: through 5.1.4.000298, fixed in 5.1.4.000309
DataDirect Connect for JDBC for PostgreSQL: through 6.0.0.001843, fixed in 6.0.0.001856
DataDirect Connect for JDBC for Progress OpenEdge: through 5.1.4.000187, fixed in 5.1.4.000189
DataDirect Connect for JDBC for Salesforce: through 6.0.0.003020, fixed in 6.0.0.003125
DataDirect Connect for JDBC for SAP HANA: through 6.0.0.000879, product retired
DataDirect Connect for JDBC for SAP S/4 HANA: through 6.0.1.001818, fixed in 6.0.1.001858
DataDirect Connect for JDBC for Sybase ASE: through 5.1.4.000161, fixed in 5.1.4.000162
DataDirect Connect for JDBC for Snowflake: through 6.0.1.001821, fixed in 6.0.1.001856
DataDirect Hybrid Data Pipeline Server: through 4.6.2.3309, fixed in 4.6.2.3430
DataDirect Hybrid Data Pipeline JDBC Driver: through 4.6.2.0607, fixed in 4.6.2.1023
DataDirect Hybrid Data Pipeline On Premises Connector: through 4.6.2.1223, fixed in 4.6.2.1339
DataDirect Hybrid Data Pipeline Docker: through 4.6.2.3316, fixed in 4.6.2.3430
DataDirect OpenAccess JDBC Driver: through 8.1.0.0177, fixed in 8.1.0.0183
DataDirect OpenAccess JDBC Driver: through 9.0.0.0019, fixed in 9.0.0.0022Das Advisory kann von community.progress.com heruntergeladen werden. Die Identifikation der Schwachstelle findet seit dem 18.09.2025 als CVE-2025-10703 statt. Sie gilt als leicht auszunutzen. Der Angriff kann über das Netzwerk passieren. Es sind weder technische Details noch ein Exploit zur Schwachstelle bekannt. Das MITRE ATT&CK Projekt deklariert die Angriffstechnik als T1059.
Ein Upgrade vermag dieses Problem zu beheben.
Once again VulDB remains the best source for vulnerability data.
Produkt
Typ
Hersteller
Name
- 4 HANA
- DataDirect Connect for JDBC Autonomous REST Connector
- DataDirect Connect for JDBC for Amazon Redshift
- DataDirect Connect for JDBC for Apache Cassandra
- DataDirect Connect for JDBC for Apache Impala
- DataDirect Connect for JDBC for Apache SparkSQL
- DataDirect Connect for JDBC for DB2
- DataDirect Connect for JDBC for Google Analytics 4
- DataDirect Connect for JDBC for Google BigQuery
- DataDirect Connect for JDBC for Greenplum
- DataDirect Connect for JDBC for Hive
- DataDirect Connect for JDBC for Informix
- DataDirect Connect for JDBC for Microsoft Dynamics 365
- DataDirect Connect for JDBC for Microsoft Sharepoint
- DataDirect Connect for JDBC for Microsoft SQLServer
- DataDirect Connect for JDBC for MongoDB
- DataDirect Connect for JDBC for MySQL
- DataDirect Connect for JDBC for OpenEdge
- DataDirect Connect for JDBC for Oracle Database
- DataDirect Connect for JDBC for Oracle Eloqua
- DataDirect Connect for JDBC for Oracle Sales Cloud
- DataDirect Connect for JDBC for Oracle Service Cloud
- DataDirect Connect for JDBC for PostgreSQL
- DataDirect Connect for JDBC for Salesforce
- DataDirect Connect for JDBC for SAP HANA
- DataDirect Connect for JDBC for SAP S
- DataDirect Connect for JDBC for Snowflake
- DataDirect Connect for JDBC for Sybase ASE
- DataDirect Hybrid Data Pipeline Docker
- DataDirect Hybrid Data Pipeline JDBC Driver
- DataDirect Hybrid Data Pipeline On Premises Connector
- DataDirect Hybrid Data Pipeline Server
- DataDirect OpenAccess JDBC Driver
Lizenz
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Zuverlässigkeit: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Zuverlässigkeit: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vektor | Komplexität | Authentisierung | Vertraulichkeit | Integrität | Verfügbarkeit |
|---|---|---|---|---|---|
| freischalten | freischalten | freischalten | freischalten | freischalten | freischalten |
| freischalten | freischalten | freischalten | freischalten | freischalten | freischalten |
| freischalten | freischalten | freischalten | freischalten | freischalten | freischalten |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Zuverlässigkeit: 🔍
Exploiting
Klasse: Erweiterte RechteCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physisch: Nein
Lokal: Nein
Remote: Ja
Verfügbarkeit: 🔒
Status: Nicht definiert
EPSS Score: 🔒
EPSS Percentile: 🔒
Preisentwicklung: 🔍
Aktuelle Preisschätzung: 🔒
| 0-Day | freischalten | freischalten | freischalten | freischalten |
|---|---|---|---|---|
| Heute | freischalten | freischalten | freischalten | freischalten |
Threat Intelligence
Interesse: 🔍Aktive Akteure: 🔍
Aktive APT Gruppen: 🔍
Gegenmassnahmen
Empfehlung: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
18.09.2025 CVE zugewiesen19.11.2025 Advisory veröffentlicht
19.11.2025 VulDB Eintrag erstellt
19.11.2025 VulDB Eintrag letzte Aktualisierung
Quellen
Advisory: community.progress.comStatus: Bestätigt
CVE: CVE-2025-10703 (🔒)
GCVE (CVE): GCVE-0-2025-10703
GCVE (VulDB): GCVE-100-332948
scip Labs: https://www.scip.ch/?labs.20171019
Eintrag
Erstellt: 19.11.2025 17:44Anpassungen: 19.11.2025 17:44 (65)
Komplett: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
Bisher keine Kommentare. Sprachen: de + en.
Bitte loggen Sie sich ein, um kommentieren zu können.