[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fkNpA1Oc8ACUJF80gZe_hHKsQim-JzEn_52owJvFTGak":3,"g5a-risk:CVE-2017-15701":128},{"success":4,"data":5,"meta":126},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":39,"epssPercentile":26,"epssTimeSeries":40,"severity":41,"affectedProducts":42,"affectedProductsCount":48,"references":49,"referencesCount":77,"weaknesses":78,"weaknessesCount":48,"isActivelyExploited":87,"cisaInfo":26,"otxData":26,"relatedBlogPosts":88,"seoMetadata":89,"configurations":114,"relatedVendorCves":124,"notableEvents":125},"CVE-2017-15701","What is CVE-2017-15701?","In Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive) the broker does not properly enforce a maximum frame size in AMQP 1.0 frames. A remote unauthenticated attacker could exploit this to cause the broker to exhaust all available memory and eventually terminate. Older AMQP protocols are not affected.","In Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive) the broker does not properly enforce a maximum frame size in AMQP 1.0 frames. A remote unaut...","2017-12-01T15:29:00.213","2025-04-20T01:37:25.86",7.5,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:N\u002FI:N\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":26,"CVSSMetricV2":29,"CVSSMetricV40":26},[16],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":25,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":25,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"3.1","NETWORK","LOW","NONE","UNCHANGED","HIGH",null,3.9,3.6,[30],{"Source":17,"Type":18,"CVSSData":31,"BaseSeverity":36,"ExploitabilityScore":37,"ImpactScore":38,"ACInsufInfo":26,"ObtainAllPrivilege":26,"ObtainUserPrivilege":26,"ObtainOtherPrivilege":26,"UserInteractionRequired":26},{"Version":32,"VectorString":33,"AccessVector":21,"AccessComplexity":22,"Authentication":23,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":34,"BaseScore":35,"BaseSeverity":26,"Exploitability":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"CollateralDamagePotential":26,"TargetDistribution":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":26,"EnvironmentalScore":26},"2.0","AV:N\u002FAC:L\u002FAu:N\u002FC:N\u002FI:N\u002FA:P","PARTIAL",5,"MEDIUM",10,2.9,0.04389,[39,39,39,39,39,39,39],"High",[43],{"vendor":44,"product":45,"version":46,"criteria":47,"vulnerable":4},"apache","qpid_broker-j","*","cpe:2.3:a:apache:qpid_broker-j:*:*:*:*:*:*:*:*",1,[50,56,62,65,69,71,73,75],{"url":51,"source":52,"tags":53},"http:\u002F\u002Fwww.securityfocus.com\u002Fbid\u002F102041","Securityfocus",[54,55],"Third Party Advisory","VDB Entry",{"url":57,"source":58,"tags":59},"https:\u002F\u002Fissues.apache.org\u002Fjira\u002Fbrowse\u002FQPID-7947","Apache",[60,61],"Issue Tracking","Vendor Advisory",{"url":63,"source":58,"tags":64},"https:\u002F\u002Flists.apache.org\u002Fthread.html\u002F4054e1c90993f337eeea24a312841c0661653e673c0ff8e2cd9520fe%40%3Cdev.qpid.apache.org%3E",[],{"url":66,"source":58,"tags":67},"https:\u002F\u002Fqpid.apache.org\u002Fcves\u002FCVE-2017-15701.html",[68,61],"Mitigation",{"url":51,"source":52,"tags":70},[54,55],{"url":57,"source":58,"tags":72},[60,61],{"url":63,"source":58,"tags":74},[],{"url":66,"source":58,"tags":76},[68,61],8,[79],{"id":80,"name":81,"description":82,"extendedDescription":83,"status":84,"abstraction":85,"structure":86},"CWE-400","Uncontrolled Resource Consumption","The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.","Limited resources include memory, file system storage, database connection pool entries, and CPU. If an attacker can trigger the allocation of these limited resources, but the number or size of the resources is not controlled, then the attacker could cause a denial of service that consumes all available resources. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system.\nThere are at least three distinct scenarios which can commonly lead to resource exhaustion:\nResource exhaustion problems are often result due to an incorrect implementation of the following situations:","Draft","Class","Simple",false,[],{"title":90,"metaDescription":91,"keywords":92,"canonicalUrl":93,"structuredData":94},"What is CVE-2017-15701? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2017-15701, a high severity cyber security vulnerability from 2017. In Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclu...","CVE-2017-15701, CVE-2017-15701 vulnerability, CVE-2017-15701 security, high 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, qpid_broker-j vulnerability","\u002Fwhat-is\u002Fcve-2017-15701",{"@context":95,"@type":96,"headline":90,"description":91,"datePublished":10,"dateModified":11,"author":97,"publisher":101,"about":105,"mainEntityOfPage":109,"articleSection":112,"keywords":113},"https:\u002F\u002Fschema.org","TechArticle",{"@type":98,"name":99,"url":100},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":98,"name":99,"url":100,"logo":102},{"@type":103,"url":104},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":106,"name":6,"description":107,"additionalType":108},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":110,"@id":111},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2017-15701","Cybersecurity","CVE-2017-15701, CVE-2017-15701 vulnerability, CVE-2017-15701 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[115],{"Operator":26,"Negate":26,"Nodes":116},[117],{"Operator":118,"Negate":26,"CPEMatch":119},"OR",[120],{"Vulnerable":4,"Criteria":47,"MatchCriteriaID":121,"VersionStartExcluding":26,"VersionStartIncluding":122,"VersionEndExcluding":26,"VersionEndIncluding":123},"84271735-DF9D-4AAF-B123-88403028D2A4","6.1.0","6.1.4",[],[],{"lastModified":11,"cacheTime":127,"version":32},1792259172394,{"score":129,"band":130,"action":131,"scoredAt":132},47,"Medium","Plan remediation","2026-10-16T06:42:59.452039+00:00"]