[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f6l2RrvyyKCCPtuVUf30bVxlDN793-w37lOTMXnZml-g":3,"g5a-risk:CVE-2020-14517":111},{"success":4,"data":5,"meta":109},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":39,"epssPercentile":27,"epssTimeSeries":40,"severity":41,"affectedProducts":42,"affectedProductsCount":48,"references":49,"referencesCount":48,"weaknesses":56,"weaknessesCount":70,"isActivelyExploited":71,"cisaInfo":27,"otxData":27,"relatedBlogPosts":72,"seoMetadata":73,"configurations":98,"relatedVendorCves":107,"notableEvents":108},"CVE-2020-14517","What is CVE-2020-14517?","Protocol encryption can be easily broken for CodeMeter (All versions prior to 6.90 are affected, including Version 6.90 or newer only if CodeMeter Runtime is running as server) and the server accepts external connections, which may allow an attacker to remotely communicate with the CodeMeter API.","Protocol encryption can be easily broken for CodeMeter (All versions prior to 6.90 are affected, including Version 6.90 or newer only if CodeMeter Runtime is...","2020-09-16T20:15:13.647","2021-11-04T18:15:08.017",9.8,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":27,"CVSSMetricV2":30,"CVSSMetricV40":27},[16],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":28,"ImpactScore":29},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":25,"AvailabilityImpact":25,"BaseScore":12,"BaseSeverity":26,"ExploitCodeMaturity":27,"RemediationLevel":27,"ReportConfidence":27,"TemporalScore":27,"TemporalSeverity":27,"ConfidentialityRequirement":27,"IntegrityRequirement":27,"AvailabilityRequirement":25,"ModifiedAttackVector":27,"ModifiedAttackComplexity":27,"ModifiedPrivilegesRequired":27,"ModifiedUserInteraction":27,"ModifiedScope":27,"ModifiedConfidentialityImpact":27,"ModifiedIntegrityImpact":27,"ModifiedAvailabilityImpact":27,"EnvironmentalScore":27,"EnvironmentalSeverity":27},"3.1","NETWORK","LOW","NONE","UNCHANGED","HIGH","CRITICAL",null,3.9,5.9,[31],{"Source":17,"Type":18,"CVSSData":32,"BaseSeverity":25,"ExploitabilityScore":37,"ImpactScore":38,"ACInsufInfo":27,"ObtainAllPrivilege":27,"ObtainUserPrivilege":27,"ObtainOtherPrivilege":27,"UserInteractionRequired":27},{"Version":33,"VectorString":34,"AccessVector":21,"AccessComplexity":22,"Authentication":23,"ConfidentialityImpact":35,"IntegrityImpact":35,"AvailabilityImpact":35,"BaseScore":36,"BaseSeverity":27,"Exploitability":27,"RemediationLevel":27,"ReportConfidence":27,"TemporalScore":27,"CollateralDamagePotential":27,"TargetDistribution":27,"ConfidentialityRequirement":27,"IntegrityRequirement":27,"AvailabilityRequirement":27,"EnvironmentalScore":27},"2.0","AV:N\u002FAC:L\u002FAu:N\u002FC:P\u002FI:P\u002FA:P","PARTIAL",7.5,10,6.4,0.00679,[39,39,39,39,39,39,39],"Critical",[43],{"vendor":44,"product":45,"version":46,"criteria":47,"vulnerable":4},"wibu","codemeter","*","cpe:2.3:a:wibu:codemeter:*:*:*:*:*:*:*:*",1,[50],{"url":51,"source":52,"tags":53},"https:\u002F\u002Fus-cert.cisa.gov\u002Fics\u002Fadvisories\u002Ficsa-20-203-01","CISA",[54,55],"Third Party Advisory","US Government Resource",[57,65],{"id":58,"name":59,"description":60,"extendedDescription":61,"status":62,"abstraction":63,"structure":64},"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":66,"name":67,"description":68,"extendedDescription":69,"status":62,"abstraction":63,"structure":64},"CWE-326","Inadequate Encryption Strength","The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.","A weak encryption scheme can be subjected to brute force attacks that have a reasonable chance of succeeding using current attack methods and resources.",2,false,[],{"title":74,"metaDescription":75,"keywords":76,"canonicalUrl":77,"structuredData":78},"What is CVE-2020-14517? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2020-14517, a critical severity cyber security vulnerability from 2020. Protocol encryption can be easily broken for CodeMeter ...","CVE-2020-14517, CVE-2020-14517 vulnerability, CVE-2020-14517 security, critical severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2020, CVSS score, exploit, patch, remediation, wibu security, codemeter vulnerability","\u002Fwhat-is\u002Fcve-2020-14517",{"@context":79,"@type":80,"headline":74,"description":75,"datePublished":10,"dateModified":11,"author":81,"publisher":85,"about":89,"mainEntityOfPage":93,"articleSection":96,"keywords":97},"https:\u002F\u002Fschema.org","TechArticle",{"@type":82,"name":83,"url":84},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":82,"name":83,"url":84,"logo":86},{"@type":87,"url":88},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":90,"name":6,"description":91,"additionalType":92},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":94,"@id":95},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2020-14517","Cybersecurity","CVE-2020-14517, CVE-2020-14517 vulnerability, CVE-2020-14517 security, critical severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[99],{"Operator":27,"Negate":27,"Nodes":100},[101],{"Operator":102,"Negate":27,"CPEMatch":103},"OR",[104],{"Vulnerable":4,"Criteria":47,"MatchCriteriaID":105,"VersionStartExcluding":27,"VersionStartIncluding":27,"VersionEndExcluding":106,"VersionEndIncluding":27},"04ECF3CE-FA64-4B81-B769-84844ED87CF7","6.90",[],[],{"lastModified":11,"cacheTime":110,"version":33},1792361941703,{"score":112,"band":113,"action":114,"scoredAt":115},54,"Medium","Plan remediation","2026-10-16T06:49:21.933804+00:00"]