[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fRGgF4Zcei--gM6Q_yDz842Ueunoux9H84EUSfBnmAaw":3,"g5a-ex:oracle\u002Fjdeveloper@*":153,"g5a-family:oracle\u002Fjdeveloper":155},{"success":4,"data":5},true,{"product":6,"versions":55,"topVulnerabilitiesByEpss":72,"kevVulnerabilities":130,"seoMetadata":131,"meta":150},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":54},"oracle","jdeveloper",16,25,0,"2022-01-18",[14,18,21,23,25,28,30,33,35,38,40,42,44,47,50,52],{"version":15,"cve_count":16,"kev_count":11,"has_kev":17},"10.1.2",2,false,{"version":19,"cve_count":20,"kev_count":11,"has_kev":17},"10.1.2.2",1,{"version":22,"cve_count":20,"kev_count":11,"has_kev":17},"10.1.2.3",{"version":24,"cve_count":20,"kev_count":11,"has_kev":17},"11.1.1.2.4",{"version":26,"cve_count":27,"kev_count":11,"has_kev":17},"11.1.1.7.0",4,{"version":29,"cve_count":16,"kev_count":11,"has_kev":17},"11.1.1.7.1",{"version":31,"cve_count":32,"kev_count":11,"has_kev":17},"11.1.1.9.0",9,{"version":34,"cve_count":27,"kev_count":11,"has_kev":17},"11.1.2.4.0",{"version":36,"cve_count":37,"kev_count":11,"has_kev":17},"12.1.3.0.0",11,{"version":39,"cve_count":16,"kev_count":11,"has_kev":17},"12.2.1.0.0",{"version":41,"cve_count":20,"kev_count":11,"has_kev":17},"12.2.1.1.0",{"version":43,"cve_count":16,"kev_count":11,"has_kev":17},"12.2.1.2.0",{"version":45,"cve_count":46,"kev_count":11,"has_kev":17},"12.2.1.3.0",13,{"version":48,"cve_count":49,"kev_count":11,"has_kev":17},"12.2.1.4.0",6,{"version":51,"cve_count":16,"kev_count":11,"has_kev":17},"9.0.4",{"version":53,"cve_count":16,"kev_count":11,"has_kev":17},"9.0.5","Jdeveloper by Oracle is a technology product with 16 tracked versions and 25 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71],{"version":15,"cve_count":16,"kev_count":11,"has_kev":17},{"version":19,"cve_count":20,"kev_count":11,"has_kev":17},{"version":22,"cve_count":20,"kev_count":11,"has_kev":17},{"version":24,"cve_count":20,"kev_count":11,"has_kev":17},{"version":26,"cve_count":27,"kev_count":11,"has_kev":17},{"version":29,"cve_count":16,"kev_count":11,"has_kev":17},{"version":31,"cve_count":32,"kev_count":11,"has_kev":17},{"version":34,"cve_count":27,"kev_count":11,"has_kev":17},{"version":36,"cve_count":37,"kev_count":11,"has_kev":17},{"version":39,"cve_count":16,"kev_count":11,"has_kev":17},{"version":41,"cve_count":20,"kev_count":11,"has_kev":17},{"version":43,"cve_count":16,"kev_count":11,"has_kev":17},{"version":45,"cve_count":46,"kev_count":11,"has_kev":17},{"version":48,"cve_count":49,"kev_count":11,"has_kev":17},{"version":51,"cve_count":16,"kev_count":11,"has_kev":17},{"version":53,"cve_count":16,"kev_count":11,"has_kev":17},[73,81,87,94,99,106,110,115,119,125],{"cveId":74,"description":75,"publishedDate":76,"cvssScore":77,"cvssVersion":78,"severity":79,"isKev":17,"epssScore":80},"CVE-2021-45105","Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.","2021-12-18",5.9,"v3.1","Medium",0.99999,{"cveId":82,"description":83,"publishedDate":84,"cvssScore":85,"cvssVersion":78,"severity":79,"isKev":17,"epssScore":86},"CVE-2020-11022","In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.","2020-04-29",6.1,0.99215,{"cveId":88,"description":89,"publishedDate":90,"cvssScore":91,"cvssVersion":78,"severity":92,"isKev":17,"epssScore":93},"CVE-2017-5645","In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.","2017-04-17",9.8,"Critical",0.89792,{"cveId":95,"description":96,"publishedDate":97,"cvssScore":85,"cvssVersion":78,"severity":79,"isKev":17,"epssScore":98},"CVE-2019-11358","jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.","2019-04-20",0.8682,{"cveId":100,"description":101,"publishedDate":102,"cvssScore":103,"cvssVersion":78,"severity":104,"isKev":17,"epssScore":105},"CVE-2021-4104","JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","2021-12-14",7.5,"High",0.80599,{"cveId":107,"description":108,"publishedDate":12,"cvssScore":91,"cvssVersion":78,"severity":92,"isKev":17,"epssScore":109},"CVE-2022-23305","By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.",0.66537,{"cveId":111,"description":112,"publishedDate":12,"cvssScore":113,"cvssVersion":78,"severity":104,"isKev":17,"epssScore":114},"CVE-2022-23302","JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.",8.8,0.63556,{"cveId":116,"description":117,"publishedDate":12,"cvssScore":113,"cvssVersion":78,"severity":104,"isKev":17,"epssScore":118},"CVE-2022-23307","CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.",0.54411,{"cveId":120,"description":121,"publishedDate":122,"cvssScore":85,"cvssVersion":123,"severity":79,"isKev":17,"epssScore":124},"CVE-2015-9251","jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text\u002Fjavascript responses to be executed.","2018-01-18","v3.0",0.29726,{"cveId":126,"description":127,"publishedDate":128,"cvssScore":103,"cvssVersion":78,"severity":104,"isKev":17,"epssScore":129},"CVE-2019-12402","The file name encoding algorithm used internally in Apache Commons Compress 1.15 to 1.18 can get into an infinite loop when faced with specially crafted inputs. This can lead to a denial of service attack if an attacker can choose the file names inside of an archive created by Compress.","2019-08-30",0.16157,[],{"title":132,"metaDescription":133,"keywords":134,"structuredData":135},"Jdeveloper by Oracle - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Jdeveloper by Oracle covering 16 versions with 25 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Jdeveloper vulnerabilities, Jdeveloper security, Jdeveloper CVE, Oracle Jdeveloper, Jdeveloper threat intelligence, Oracle security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":136,"@type":137,"name":138,"description":133,"url":139,"manufacturer":140,"applicationCategory":144,"softwareVersion":145,"mainEntity":146},"https:\u002F\u002Fschema.org","SoftwareApplication","Jdeveloper","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Foracle\u002Fjdeveloper",{"@type":141,"name":142,"url":143},"Organization","Oracle","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Foracle","Security Software","16 versions tracked",{"@type":147,"name":148,"description":149,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","Jdeveloper Security Vulnerabilities","Security vulnerabilities affecting Jdeveloper by Oracle",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":151,"apiVersion":152},"2026-10-18T00:55:45.050Z","3.0",{"rows":154,"total":11,"capped":17,"failed":11},[],[156],{"product":157,"cves":20},"jdeveloper_and_adf"]