[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcg2MEe_ciEK5rlRRLsW0EDA3RZFQqpx2zN4-8mVPYCc":3,"g5a-risk:CVE-2022-22190":120},{"success":4,"data":5,"meta":118},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":49,"epssPercentile":26,"epssTimeSeries":50,"severity":51,"affectedProducts":52,"affectedProductsCount":58,"references":59,"referencesCount":58,"weaknesses":65,"weaknessesCount":80,"isActivelyExploited":81,"cisaInfo":26,"otxData":26,"relatedBlogPosts":82,"seoMetadata":83,"configurations":108,"relatedVendorCves":116,"notableEvents":117},"CVE-2022-22190","What is CVE-2022-22190?","An Improper Access Control vulnerability in the Juniper Networks Paragon Active Assurance Control Center allows an unauthenticated attacker to leverage a crafted URL to generate PDF reports, potentially containing sensitive configuration information. A feature was introduced in version 3.1 of the Paragon Active Assurance Control Center which allows users to selective share account data using a unique identifier. Knowing the proper format of the URL and the identifier of an existing object in an application it is possible to get access to that object without being logged in, even if the object is not shared, resulting in the opportunity for malicious exfiltration of user data. Note that the Paragon Active Assurance Control Center SaaS offering is not affected by this issue. This issue affects Juniper Networks Paragon Active Assurance version 3.1.0.","An Improper Access Control vulnerability in the Juniper Networks Paragon Active Assurance Control Center allows an unauthenticated attacker to leverage a cra...","2022-04-14T16:15:08.23","2023-06-27T19:01:00.173",7.5,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N",{"CVSSMetricV31":15,"CVSSMetricV30":26,"CVSSMetricV2":39,"CVSSMetricV40":26},[16,29],{"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":25,"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","HIGH",null,3.9,3.6,{"Source":30,"Type":31,"CVSSData":32,"ExploitabilityScore":37,"ImpactScore":38},"sirt@juniper.net","Secondary",{"Version":20,"VectorString":33,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":34,"Scope":35,"ConfidentialityImpact":25,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":36,"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},"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:H\u002FI:N\u002FA:N","REQUIRED","CHANGED",7.4,2.8,4,[40],{"Source":17,"Type":18,"CVSSData":41,"BaseSeverity":44,"ExploitabilityScore":47,"ImpactScore":48,"ACInsufInfo":26,"ObtainAllPrivilege":26,"ObtainUserPrivilege":26,"ObtainOtherPrivilege":26,"UserInteractionRequired":26},{"Version":42,"VectorString":43,"AccessVector":21,"AccessComplexity":44,"Authentication":23,"ConfidentialityImpact":45,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":46,"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:M\u002FAu:N\u002FC:P\u002FI:N\u002FA:N","MEDIUM","PARTIAL",4.3,8.6,2.9,0.00961,[49,49,49,49,49,49,49],"High",[53],{"vendor":54,"product":55,"version":56,"criteria":57,"vulnerable":4},"juniper","paragon_active_assurance_control_center","3.1.0","cpe:2.3:a:juniper:paragon_active_assurance_control_center:3.1.0:*:*:*:*:*:*:*",1,[60],{"url":61,"source":62,"tags":63},"https:\u002F\u002Fkb.juniper.net\u002FJSA69500","Juniper",[64],"Vendor Advisory",[66,74],{"id":67,"name":68,"description":69,"extendedDescription":70,"status":71,"abstraction":72,"structure":73},"CWE-284","Improper Access Control","The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.","Access control involves the use of several protection mechanisms such as:\nWhen any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc.\nThere are two distinct behaviors that can introduce access control weaknesses:","Incomplete","Pillar","Simple",{"id":75,"name":76,"description":77,"extendedDescription":78,"status":71,"abstraction":79,"structure":73},"CWE-639","Authorization Bypass Through User-Controlled Key","The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.","Retrieval of a user record occurs in the system based on some key value that is under user control. The key would typically identify a user-related record stored in the system and would be used to lookup that record for presentation to the user. It is likely that an attacker would have to be an authenticated user in the system. However, the authorization process would not properly check the data access operation to ensure that the authenticated user performing the operation has sufficient entitlements to perform the requested data access, hence bypassing any other authorization checks present in the system.\nFor example, attackers can look at places where user specific data is retrieved (e.g. search screens) and determine whether the key for the item being looked up is controllable externally. The key may be a hidden field in the HTML form field, might be passed as a URL parameter or as an unencrypted cookie variable, then in each of these cases it will be possible to tamper with the key value.\nOne manifestation of this weakness is when a system uses sequential or otherwise easily-guessable session IDs that would allow one user to easily switch to another user's session and read\u002Fmodify their data.","Base",2,false,[],{"title":84,"metaDescription":85,"keywords":86,"canonicalUrl":87,"structuredData":88},"What is CVE-2022-22190? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2022-22190, a high severity cyber security vulnerability from 2022. An Improper Access Control vulnerability in the Juniper Net...","CVE-2022-22190, CVE-2022-22190 vulnerability, CVE-2022-22190 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2022, CVSS score, exploit, patch, remediation, juniper security, paragon_active_assurance_control_center vulnerability","\u002Fwhat-is\u002Fcve-2022-22190",{"@context":89,"@type":90,"headline":84,"description":85,"datePublished":10,"dateModified":11,"author":91,"publisher":95,"about":99,"mainEntityOfPage":103,"articleSection":106,"keywords":107},"https:\u002F\u002Fschema.org","TechArticle",{"@type":92,"name":93,"url":94},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":92,"name":93,"url":94,"logo":96},{"@type":97,"url":98},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":100,"name":6,"description":101,"additionalType":102},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":104,"@id":105},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2022-22190","Cybersecurity","CVE-2022-22190, CVE-2022-22190 vulnerability, CVE-2022-22190 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[109],{"Operator":26,"Negate":26,"Nodes":110},[111],{"Operator":112,"Negate":26,"CPEMatch":113},"OR",[114],{"Vulnerable":4,"Criteria":57,"MatchCriteriaID":115,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"88D33CE1-99FB-4228-A8A2-544E9307E9C9",[],[],{"lastModified":11,"cacheTime":119,"version":42},1792255529795,{"score":121,"band":122,"action":123,"scoredAt":124},47,"Medium","Plan remediation","2026-10-16T06:54:09.60031+00:00"]