[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f_s0p7P7lrAGJs16js-Ig1cUYH_KdYYrlsCwWFyay7fo":3,"g5a-risk:CVE-2016-6798":114},{"success":4,"data":5,"meta":112},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":39,"epssPercentile":15,"epssTimeSeries":40,"severity":41,"affectedProducts":42,"affectedProductsCount":48,"references":49,"referencesCount":64,"weaknesses":65,"weaknessesCount":48,"isActivelyExploited":74,"cisaInfo":15,"otxData":15,"relatedBlogPosts":75,"seoMetadata":76,"configurations":101,"relatedVendorCves":110,"notableEvents":111},"CVE-2016-6798","What is CVE-2016-6798?","In the XSS Protection API module before 1.0.12 in Apache Sling, the method XSS.getValidXML() uses an insecure SAX parser to validate the input string, which allows for XXE attacks in all scripts which use this method to validate user input, potentially allowing an attacker to read sensitive data on the filesystem, perform same-site-request-forgery (SSRF), port-scanning behind the firewall or DoS the application.","In the XSS Protection API module before 1.0.12 in Apache Sling, the method XSS.getValidXML() uses an insecure SAX parser to validate the input string, which ...","2017-07-19T15:29:00.213","2025-04-20T01:37:25.86",9.8,"CVSS:3.0\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":16,"CVSSMetricV2":30,"CVSSMetricV40":15},null,[17],{"Source":18,"Type":19,"CVSSData":20,"ExploitabilityScore":28,"ImpactScore":29},"nvd@nist.gov","Primary",{"Version":21,"VectorString":13,"AttackVector":22,"AttackComplexity":23,"PrivilegesRequired":24,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":26,"IntegrityImpact":26,"AvailabilityImpact":26,"BaseScore":12,"BaseSeverity":27,"ExploitCodeMaturity":15,"RemediationLevel":15,"ReportConfidence":15,"TemporalScore":15,"TemporalSeverity":15,"ConfidentialityRequirement":15,"IntegrityRequirement":15,"AvailabilityRequirement":15,"ModifiedAttackVector":15,"ModifiedAttackComplexity":15,"ModifiedPrivilegesRequired":15,"ModifiedUserInteraction":15,"ModifiedScope":15,"ModifiedConfidentialityImpact":15,"ModifiedIntegrityImpact":15,"ModifiedAvailabilityImpact":15,"EnvironmentalScore":15,"EnvironmentalSeverity":15},"3.0","NETWORK","LOW","NONE","UNCHANGED","HIGH","CRITICAL",3.9,5.9,[31],{"Source":18,"Type":19,"CVSSData":32,"BaseSeverity":26,"ExploitabilityScore":37,"ImpactScore":38,"ACInsufInfo":15,"ObtainAllPrivilege":15,"ObtainUserPrivilege":15,"ObtainOtherPrivilege":15,"UserInteractionRequired":15},{"Version":33,"VectorString":34,"AccessVector":22,"AccessComplexity":23,"Authentication":24,"ConfidentialityImpact":35,"IntegrityImpact":35,"AvailabilityImpact":35,"BaseScore":36,"BaseSeverity":15,"Exploitability":15,"RemediationLevel":15,"ReportConfidence":15,"TemporalScore":15,"CollateralDamagePotential":15,"TargetDistribution":15,"ConfidentialityRequirement":15,"IntegrityRequirement":15,"AvailabilityRequirement":15,"EnvironmentalScore":15},"2.0","AV:N\u002FAC:L\u002FAu:N\u002FC:P\u002FI:P\u002FA:P","PARTIAL",7.5,10,6.4,0.03669,[39,39,39,39,39,39,39],"Critical",[43],{"vendor":44,"product":45,"version":46,"criteria":47,"vulnerable":4},"apache","sling","*","cpe:2.3:a:apache:sling:*:*:*:*:*:*:*:*",1,[50,56,60,62],{"url":51,"source":52,"tags":53},"http:\u002F\u002Fwww.securityfocus.com\u002Fbid\u002F99873","Securityfocus",[54,55],"Third Party Advisory","VDB Entry",{"url":57,"source":58,"tags":59},"https:\u002F\u002Flists.apache.org\u002Fthread.html\u002Fb72c3a511592ec70729b3ec2d29302b6ce87bbeab62d4745617a6bd0%40%3Cdev.sling.apache.org%3E","Apache",[],{"url":51,"source":52,"tags":61},[54,55],{"url":57,"source":58,"tags":63},[],4,[66],{"id":67,"name":68,"description":69,"extendedDescription":70,"status":71,"abstraction":72,"structure":73},"CWE-611","Improper Restriction of XML External Entity Reference","The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.","XML documents optionally contain a Document Type Definition (DTD), which, among other features, enables the definition of XML entities. It is possible to define an entity by providing a substitution string in the form of a URI. The XML parser can access the contents of this URI and embed these contents back into the XML document for further processing.\nBy submitting an XML file that defines an external entity with a file:\u002F\u002F URI, an attacker can cause the processing application to read the contents of a local file. For example, a URI such as \"file:\u002F\u002F\u002Fc:\u002Fwinnt\u002Fwin.ini\" designates (in Windows) the file C:\\Winnt\\win.ini, or file:\u002F\u002F\u002Fetc\u002Fpasswd designates the password file in Unix-based systems. Using URIs with other schemes such as http:\u002F\u002F, the attacker can force the application to make outgoing requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions or hide the source of attacks such as port scanning.\nOnce the content of the URI is read, it is fed back into the application that is processing the XML. This application may echo back the data (e.g. in an error message), thereby exposing the file contents.","Draft","Base","Simple",false,[],{"title":77,"metaDescription":78,"keywords":79,"canonicalUrl":80,"structuredData":81},"What is CVE-2016-6798? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2016-6798, a critical severity cyber security vulnerability from 2017. In the XSS Protection API module before 1.0.12 in Apache...","CVE-2016-6798, CVE-2016-6798 vulnerability, CVE-2016-6798 security, critical severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2017, CVSS score, exploit, patch, remediation, apache security, sling vulnerability","\u002Fwhat-is\u002Fcve-2016-6798",{"@context":82,"@type":83,"headline":77,"description":78,"datePublished":10,"dateModified":11,"author":84,"publisher":88,"about":92,"mainEntityOfPage":96,"articleSection":99,"keywords":100},"https:\u002F\u002Fschema.org","TechArticle",{"@type":85,"name":86,"url":87},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":85,"name":86,"url":87,"logo":89},{"@type":90,"url":91},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":93,"name":6,"description":94,"additionalType":95},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":97,"@id":98},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2016-6798","Cybersecurity","CVE-2016-6798, CVE-2016-6798 vulnerability, CVE-2016-6798 security, critical severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[102],{"Operator":15,"Negate":15,"Nodes":103},[104],{"Operator":105,"Negate":15,"CPEMatch":106},"OR",[107],{"Vulnerable":4,"Criteria":47,"MatchCriteriaID":108,"VersionStartExcluding":15,"VersionStartIncluding":15,"VersionEndExcluding":15,"VersionEndIncluding":109},"C2A62F4D-F969-446E-8A2B-BD817101880F","1.0.10",[],[],{"lastModified":11,"cacheTime":113,"version":33},1792355977084,{"score":115,"band":116,"action":117,"scoredAt":118},56,"Medium","Plan remediation","2026-10-17T09:06:34.014026+00:00"]