[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fND2b-RBJ7swq4TLCqV3itYHPnhq13rdxBbf40gJ02j0":3,"g5a-risk:CVE-2021-31352":112},{"success":4,"data":5,"meta":110},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":48,"weaknesses":57,"weaknessesCount":71,"isActivelyExploited":72,"cisaInfo":26,"otxData":26,"relatedBlogPosts":73,"seoMetadata":74,"configurations":99,"relatedVendorCves":108,"notableEvents":109},"CVE-2021-31352","What is CVE-2021-31352?","An Information Exposure vulnerability in Juniper Networks SRC Series devices configured for NETCONF over SSH permits the negotiation of weak ciphers, which could allow a remote attacker to obtain sensitive information. A remote attacker with read and write access to network data could exploit this vulnerability to display plaintext bits from a block of ciphertext and obtain sensitive information. This issue affects all Juniper Networks SRC Series versions prior to 4.13.0-R6.","An Information Exposure vulnerability in Juniper Networks SRC Series devices configured for NETCONF over SSH permits the negotiation of weak ciphers, which c...","2021-10-19T19:15:08.66","2022-10-27T13:05:14.193",5.3,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:L\u002FI:N\u002FA:N",{"CVSSMetricV31":15,"CVSSMetricV30":26,"CVSSMetricV2":29,"CVSSMetricV40":26},[16],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":27,"ImpactScore":28},"sirt@juniper.net","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":22,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":12,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":23,"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","MEDIUM",null,3.9,1.4,[30],{"Source":31,"Type":18,"CVSSData":32,"BaseSeverity":25,"ExploitabilityScore":37,"ImpactScore":38,"ACInsufInfo":26,"ObtainAllPrivilege":26,"ObtainUserPrivilege":26,"ObtainOtherPrivilege":26,"UserInteractionRequired":26},"nvd@nist.gov",{"Version":33,"VectorString":34,"AccessVector":21,"AccessComplexity":22,"Authentication":23,"ConfidentialityImpact":35,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":36,"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:P\u002FI:N\u002FA:N","PARTIAL",5,10,2.9,0.00834,[39,39,39,39,39,39,39],"Medium",[43],{"vendor":44,"product":45,"version":46,"criteria":47,"vulnerable":4},"juniper","session_and_resource_control","*","cpe:2.3:a:juniper:session_and_resource_control:*:*:*:*:*:*:*:*",1,[50],{"url":51,"source":52,"tags":53},"https:\u002F\u002Fkb.juniper.net\u002FJSA11217","Juniper",[54,55,56],"Exploit","Patch","Vendor Advisory",[58,66],{"id":59,"name":60,"description":61,"extendedDescription":62,"status":63,"abstraction":64,"structure":65},"CWE-200","Exposure of Sensitive Information to an Unauthorized Actor","The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.","There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker.  Some kinds of sensitive information include:\nInformation might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected.  These parties include:\nInformation exposures can occur in different ways:\nIt is common practice to describe any loss of confidentiality as an \"information exposure,\" but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read.  CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.","Draft","Class","Simple",{"id":67,"name":68,"description":69,"extendedDescription":70,"status":63,"abstraction":64,"structure":65},"CWE-327","Use of a Broken or Risky Cryptographic Algorithm","The product uses a broken or risky cryptographic algorithm or protocol.","Cryptographic algorithms are the methods by which data is scrambled to prevent observation or influence by unauthorized actors. Insecure cryptography can be exploited to expose sensitive information, modify data in unexpected ways, spoof identities of other users or devices, or other impacts.\nIt is very difficult to produce a secure algorithm, and even high-profile algorithms by accomplished cryptographic experts have been broken. Well-known techniques exist to break or weaken various kinds of cryptography. Accordingly, there are a small number of well-understood and heavily studied algorithms that should be used by most products. Using a non-standard or known-insecure algorithm is dangerous because a determined adversary may be able to break the algorithm and compromise whatever data has been protected.\nSince the state of cryptography advances so rapidly, it is common for an algorithm to be considered \"unsafe\" even if it was once thought to be strong. This can happen when new attacks are discovered, or if computing power increases so much that the cryptographic algorithm no longer provides the amount of protection that was originally thought.\nFor a number of reasons, this weakness is even more challenging to manage with hardware deployment of cryptographic algorithms as opposed to software implementation. First, if a flaw is discovered with hardware-implemented cryptography, the flaw cannot be fixed in most cases without a recall of the product, because hardware is not easily replaceable like software. Second, because the hardware product is expected to work for years, the adversary's computing power will only increase over time.",2,false,[],{"title":75,"metaDescription":76,"keywords":77,"canonicalUrl":78,"structuredData":79},"What is CVE-2021-31352? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2021-31352, a medium severity cyber security vulnerability from 2021. An Information Exposure vulnerability in Juniper Networks...","CVE-2021-31352, CVE-2021-31352 vulnerability, CVE-2021-31352 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2021, CVSS score, exploit, patch, remediation, juniper security, session_and_resource_control vulnerability","\u002Fwhat-is\u002Fcve-2021-31352",{"@context":80,"@type":81,"headline":75,"description":76,"datePublished":10,"dateModified":11,"author":82,"publisher":86,"about":90,"mainEntityOfPage":94,"articleSection":97,"keywords":98},"https:\u002F\u002Fschema.org","TechArticle",{"@type":83,"name":84,"url":85},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":83,"name":84,"url":85,"logo":87},{"@type":88,"url":89},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":91,"name":6,"description":92,"additionalType":93},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":95,"@id":96},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2021-31352","Cybersecurity","CVE-2021-31352, CVE-2021-31352 vulnerability, CVE-2021-31352 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[100],{"Operator":26,"Negate":26,"Nodes":101},[102],{"Operator":103,"Negate":26,"CPEMatch":104},"OR",[105],{"Vulnerable":4,"Criteria":47,"MatchCriteriaID":106,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":107,"VersionEndIncluding":26},"F859871E-2194-4F8D-8978-26A032CF77D1","4.130r6",[],[],{"lastModified":11,"cacheTime":111,"version":33},1792255378404,{"score":113,"band":41,"action":114,"scoredAt":115},43,"Plan remediation","2026-10-16T06:52:16.103121+00:00"]