[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fWYvVZJM0PTfYhUOkshpt-jAIBR6Ftk0pod29TW8LXhU":3,"g5a-ex:oracle\u002Fcommunications_network_integrity@*":108,"g5a-family:oracle\u002Fcommunications_network_integrity":110},{"success":4,"data":5},true,{"product":6,"versions":24,"topVulnerabilitiesByEpss":28,"kevVulnerabilities":85,"seoMetadata":86,"meta":105},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":23},"oracle","communications_network_integrity",3,24,0,"2022-01-18",[14,17,20],{"version":15,"cve_count":9,"kev_count":11,"has_kev":16},"7.3.2",false,{"version":18,"cve_count":19,"kev_count":11,"has_kev":16},"7.3.5",8,{"version":21,"cve_count":22,"kev_count":11,"has_kev":16},"7.3.6",17,"Communications Network Integrity by Oracle is a technology product with 3 tracked versions and 24 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[25,26,27],{"version":15,"cve_count":9,"kev_count":11,"has_kev":16},{"version":18,"cve_count":19,"kev_count":11,"has_kev":16},{"version":21,"cve_count":22,"kev_count":11,"has_kev":16},[29,37,44,51,56,61,66,70,75,79],{"cveId":30,"description":31,"publishedDate":32,"cvssScore":33,"cvssVersion":34,"severity":35,"isKev":16,"epssScore":36},"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":38,"description":39,"publishedDate":40,"cvssScore":41,"cvssVersion":34,"severity":42,"isKev":16,"epssScore":43},"CVE-2019-0227","A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.","2019-05-01",7.5,"High",0.9194,{"cveId":45,"description":46,"publishedDate":47,"cvssScore":48,"cvssVersion":34,"severity":49,"isKev":16,"epssScore":50},"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":52,"description":53,"publishedDate":54,"cvssScore":48,"cvssVersion":34,"severity":49,"isKev":16,"epssScore":55},"CVE-2019-2729","Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Web Services). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0 and 12.2.1.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H).","2019-06-19",0.8883,{"cveId":57,"description":58,"publishedDate":59,"cvssScore":41,"cvssVersion":34,"severity":42,"isKev":16,"epssScore":60},"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",0.80599,{"cveId":62,"description":63,"publishedDate":64,"cvssScore":48,"cvssVersion":34,"severity":49,"isKev":16,"epssScore":65},"CVE-2019-17571","Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.","2019-12-20",0.6998,{"cveId":67,"description":68,"publishedDate":12,"cvssScore":48,"cvssVersion":34,"severity":49,"isKev":16,"epssScore":69},"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":71,"description":72,"publishedDate":12,"cvssScore":73,"cvssVersion":34,"severity":42,"isKev":16,"epssScore":74},"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":76,"description":77,"publishedDate":12,"cvssScore":73,"cvssVersion":34,"severity":42,"isKev":16,"epssScore":78},"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":80,"description":81,"publishedDate":82,"cvssScore":83,"cvssVersion":34,"severity":42,"isKev":16,"epssScore":84},"CVE-2019-10086","In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean.","2019-08-20",7.3,0.28384,[],{"title":87,"metaDescription":88,"keywords":89,"structuredData":90},"Communications Network Integrity by Oracle - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Communications Network Integrity by Oracle covering 3 versions with 24 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Communications Network Integrity vulnerabilities, Communications Network Integrity security, Communications Network Integrity CVE, Oracle Communications Network Integrity, Communications Network Integrity threat intelligence, Oracle security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":91,"@type":92,"name":93,"description":88,"url":94,"manufacturer":95,"applicationCategory":99,"softwareVersion":100,"mainEntity":101},"https:\u002F\u002Fschema.org","SoftwareApplication","Communications Network Integrity","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Foracle\u002Fcommunications_network_integrity",{"@type":96,"name":97,"url":98},"Organization","Oracle","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Foracle","Security Software","3 versions tracked",{"@type":102,"name":103,"description":104,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","Communications Network Integrity Security Vulnerabilities","Security vulnerabilities affecting Communications Network Integrity by Oracle",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":106,"apiVersion":107},"2026-10-17T19:27:00.692Z","3.0",{"rows":109,"total":11,"capped":16,"failed":11},[],[]]