Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10703: CWE-94 Improper Control of Generation of Code ('Code Injection') in Progress DataDirect Connect for JDBC for Amazon Redshift

0
High
VulnerabilityCVE-2025-10703cvecve-2025-10703cwe-94
Published: Wed Nov 19 2025 (11/19/2025, 15:47:07 UTC)
Source: CVE Database V5
Vendor/Project: Progress
Product: DataDirect Connect for JDBC for Amazon Redshift

Description

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.0022

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 06:26:17 UTC

Technical Analysis

CVE-2025-10703 is a critical code injection vulnerability categorized under CWE-94, impacting Progress DataDirect Connect for JDBC drivers and related products. The root cause lies in the SpyAttribute connection option, which permits specifying a log file path for the JDBC driver’s logging output. If an application allows end users to set this option, an attacker can inject arbitrary JavaScript code into the log file. When the log file is placed in a location accessible by the application server and served as a resource, the malicious script can be executed remotely, effectively enabling remote code execution (RCE). This vulnerability affects numerous DataDirect JDBC drivers for various databases including Amazon Redshift, Apache Cassandra, Hive, Microsoft SQL Server, Oracle, PostgreSQL, and others, as well as the DataDirect Hybrid Data Pipeline and OpenAccess JDBC drivers. The flaw exists in versions prior to the fixed releases listed, with no authentication or user interaction required for exploitation. The vulnerability’s CVSS 4.0 score is 8.6, reflecting its high impact on confidentiality, integrity, and availability, combined with ease of exploitation. Although no exploits have been observed in the wild yet, the broad product impact and potential for severe damage necessitate immediate remediation. The vulnerability allows attackers to leverage logging mechanisms to inject and execute malicious code, posing significant risks to data confidentiality and system integrity in environments using these drivers.

Potential Impact

The impact of CVE-2025-10703 is substantial for organizations worldwide that utilize Progress DataDirect Connect for JDBC drivers or related products in their data access infrastructure. Successful exploitation can lead to remote code execution on application servers, enabling attackers to execute arbitrary JavaScript code. This can result in data theft, unauthorized access, system compromise, and potential lateral movement within networks. The vulnerability undermines confidentiality by exposing sensitive data through malicious scripts, compromises integrity by allowing unauthorized code execution, and threatens availability if attackers disrupt services. Given the wide range of affected database platforms and the common use of these JDBC drivers in enterprise environments, the scope of affected systems is broad. The lack of required authentication and user interaction lowers the barrier to exploitation, increasing risk. Organizations with web-facing applications or services that log user-controlled input via these drivers are particularly vulnerable. The potential for exploitation in cloud, on-premises, and hybrid environments further amplifies the threat. Without timely patching, attackers could leverage this vulnerability to establish persistent footholds, exfiltrate data, or disrupt critical business operations.

Mitigation Recommendations

To mitigate CVE-2025-10703, organizations should immediately upgrade all affected Progress DataDirect Connect for JDBC drivers and related products to the fixed versions specified by the vendor. Specifically, ensure that versions are at or beyond the fixed releases listed for each affected product. Additionally, audit all applications and services using these JDBC drivers to verify that the SpyAttribute connection option is not exposed to untrusted end users or external inputs. Implement strict input validation and sanitization controls to prevent injection of malicious values into logging configuration parameters. Restrict file system permissions and web server configurations to prevent log files from being served as executable resources or accessible via HTTP endpoints. Employ application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block suspicious log file access or script execution attempts. Conduct thorough security reviews of logging practices to avoid writing logs to web-accessible directories. Finally, monitor logs and network traffic for any signs of exploitation attempts or anomalous behavior related to this vulnerability. Establish incident response plans to quickly address any detected exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
ProgressSoftware
Date Reserved
2025-09-18T19:40:28.783Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 691de8ff964c14ffeea99620

Added to database: 11/19/2025, 3:57:51 PM

Last enriched: 2/27/2026, 6:26:17 AM

Last updated: 3/23/2026, 4:55:23 AM

Views: 99

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses