[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fXbQKE8j_RQtoMWyvm7yyjbAVCUw7Iatxo4m3AsDf-F4":3,"g5a-risk:CVE-2019-0030":139},{"success":4,"data":5,"meta":137},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":50,"epssPercentile":26,"epssTimeSeries":51,"severity":52,"affectedProducts":53,"affectedProductsCount":66,"references":67,"referencesCount":73,"weaknesses":74,"weaknessesCount":90,"isActivelyExploited":91,"cisaInfo":26,"otxData":26,"relatedBlogPosts":92,"seoMetadata":93,"configurations":118,"relatedVendorCves":135,"notableEvents":136},"CVE-2019-0030","What is CVE-2019-0030?","Juniper ATP uses DES and a hardcoded salt for password hashing, allowing for trivial de-hashing of the password file contents. This issue affects Juniper ATP 5.0 versions prior to 5.0.3.","Juniper ATP uses DES and a hardcoded salt for password hashing, allowing for trivial de-hashing of the password file contents. This issue affects Juniper ATP...","2019-01-15T21:29:02.027","2023-11-07T03:01:39.983",7.2,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:H\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":29,"CVSSMetricV2":40,"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":24,"Scope":25,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":12,"BaseSeverity":23,"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","HIGH","NONE","UNCHANGED",null,1.2,5.9,[30],{"Source":31,"Type":32,"CVSSData":33,"ExploitabilityScore":39,"ImpactScore":28},"8cbe9d5a-a066-4c94-8978-4b15efeae968","Secondary",{"Version":34,"VectorString":35,"AttackVector":36,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":23,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":37,"BaseSeverity":38,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":26,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"3.0","CVSS:3.0\u002FAV:L\u002FAC:L\u002FPR:H\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H","LOCAL",6.7,"MEDIUM",0.8,[41],{"Source":17,"Type":18,"CVSSData":42,"BaseSeverity":38,"ExploitabilityScore":48,"ImpactScore":49,"ACInsufInfo":26,"ObtainAllPrivilege":26,"ObtainUserPrivilege":26,"ObtainOtherPrivilege":26,"UserInteractionRequired":26},{"Version":43,"VectorString":44,"AccessVector":21,"AccessComplexity":22,"Authentication":45,"ConfidentialityImpact":46,"IntegrityImpact":24,"AvailabilityImpact":24,"BaseScore":47,"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:S\u002FC:P\u002FI:N\u002FA:N","SINGLE","PARTIAL",4,8,2.9,0.00534,[50,50,50,50,50,50,50],"High",[54,59,63],{"vendor":55,"product":56,"version":57,"criteria":58,"vulnerable":4},"juniper","advanced_threat_prevention_firmware","*","cpe:2.3:o:juniper:advanced_threat_prevention_firmware:*:*:*:*:*:*:*:*",{"vendor":55,"product":60,"version":61,"criteria":62,"vulnerable":4},"atp400","-","cpe:2.3:h:juniper:atp400:-:*:*:*:*:*:*:*",{"vendor":55,"product":64,"version":61,"criteria":65,"vulnerable":4},"atp700","cpe:2.3:h:juniper:atp700:-:*:*:*:*:*:*:*",3,[68],{"url":69,"source":70,"tags":71},"https:\u002F\u002Fkb.juniper.net\u002FJSA10918","Juniper",[72],"Vendor Advisory",1,[75,83],{"id":76,"name":77,"description":78,"extendedDescription":79,"status":80,"abstraction":81,"structure":82},"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.","Draft","Class","Simple",{"id":84,"name":85,"description":86,"extendedDescription":87,"status":88,"abstraction":89,"structure":82},"CWE-916","Use of Password Hash With Insufficient Computational Effort","The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive.","Many password storage mechanisms compute a hash and store the hash, instead of storing the original password in plaintext. In this design, authentication involves accepting an incoming password, computing its hash, and comparing it to the stored hash.\nMany hash algorithms are designed to execute quickly with minimal overhead, even cryptographic hashes. However, this efficiency is a problem for password storage, because it can reduce an attacker's workload for brute-force password cracking. If an attacker can obtain the hashes through some other method (such as SQL injection on a database that stores hashes), then the attacker can store the hashes offline and use various techniques to crack the passwords by computing hashes efficiently. Without a built-in workload, modern attacks can compute large numbers of hashes, or even exhaust the entire space of all possible passwords, within a very short amount of time, using massively-parallel computing (such as cloud computing) and GPU, ASIC, or FPGA hardware. In such a scenario, an efficient hash algorithm helps the attacker.\nThere are several properties of a hash scheme that are relevant to its strength against an offline, massively-parallel attack:\nNote that the security requirements for the product may vary depending on the environment and the value of the passwords. Different schemes might not provide all of these properties, yet may still provide sufficient security for the environment. Conversely, a solution might be very strong in preserving one property, which still being very weak for an attack against another property, or it might not be able to significantly reduce the efficiency of a massively-parallel attack.","Incomplete","Base",2,false,[],{"title":94,"metaDescription":95,"keywords":96,"canonicalUrl":97,"structuredData":98},"What is CVE-2019-0030? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2019-0030, a high severity cyber security vulnerability from 2019. Juniper ATP uses DES and a hardcoded salt for password hashi...","CVE-2019-0030, CVE-2019-0030 vulnerability, CVE-2019-0030 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2019, CVSS score, exploit, patch, remediation, juniper security, advanced_threat_prevention_firmware vulnerability, atp400 vulnerability, atp700 vulnerability","\u002Fwhat-is\u002Fcve-2019-0030",{"@context":99,"@type":100,"headline":94,"description":95,"datePublished":10,"dateModified":11,"author":101,"publisher":105,"about":109,"mainEntityOfPage":113,"articleSection":116,"keywords":117},"https:\u002F\u002Fschema.org","TechArticle",{"@type":102,"name":103,"url":104},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":102,"name":103,"url":104,"logo":106},{"@type":107,"url":108},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":110,"name":6,"description":111,"additionalType":112},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":114,"@id":115},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2019-0030","Cybersecurity","CVE-2019-0030, CVE-2019-0030 vulnerability, CVE-2019-0030 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[119],{"Operator":120,"Negate":26,"Nodes":121},"AND",[122,129],{"Operator":123,"Negate":26,"CPEMatch":124},"OR",[125],{"Vulnerable":4,"Criteria":58,"MatchCriteriaID":126,"VersionStartExcluding":26,"VersionStartIncluding":127,"VersionEndExcluding":128,"VersionEndIncluding":26},"EADD63C7-4637-4649-9F45-A68E983B2610","5.0.0","5.0.3",{"Operator":123,"Negate":26,"CPEMatch":130},[131,133],{"Vulnerable":26,"Criteria":62,"MatchCriteriaID":132,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"0A96949A-031D-4E05-8915-1A6D6BE645E0",{"Vulnerable":26,"Criteria":65,"MatchCriteriaID":134,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"29D8A7A3-2DFB-4752-8509-451247A1D5D1",[],[],{"lastModified":11,"cacheTime":138,"version":43},1792255541586,{"score":140,"band":141,"action":142,"scoredAt":143},46,"Medium","Plan remediation","2026-10-16T06:45:24.750526+00:00"]