[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fPXbtsIOwA8QFjhnYSsNe2v0Z0YWPNNz-JCTDjFRaVXk":3,"g5a-risk:CVE-2018-20167":116},{"success":4,"data":5,"meta":114},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":41,"epssPercentile":15,"epssTimeSeries":42,"severity":43,"affectedProducts":44,"affectedProductsCount":50,"references":51,"referencesCount":66,"weaknesses":67,"weaknessesCount":50,"isActivelyExploited":76,"cisaInfo":15,"otxData":15,"relatedBlogPosts":77,"seoMetadata":78,"configurations":103,"relatedVendorCves":112,"notableEvents":113},"CVE-2018-20167","What is CVE-2018-20167?","Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe \"cat README.md\" command when \\e}pn is used. A popmedia control sequence can allow the malicious execution of executable file formats registered in the X desktop share MIME types (\u002Fusr\u002Fshare\u002Fapplications). The control sequence defers unknown file types to the handle_unknown_media() function, which executes xdg-open against the filename specified in the sequence. The use of xdg-open for all unknown file types allows executable file formats with a registered shared MIME type to be executed. An attacker can achieve remote code execution by introducing an executable file and a plain text file containing the control sequence through a fake software project (e.g., in Git or a tarball). When the control sequence is rendered (such as with cat), the executable file will be run.","Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe \"cat README.md\" command when \\e}pn is used...","2018-12-17T05:29:00.957","2019-10-03T00:03:26.223",7.8,"CVSS:3.0\u002FAV:L\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:U\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":15,"CVSSMetricV30":16,"CVSSMetricV2":30,"CVSSMetricV40":15},null,[17],{"Source":18,"Type":19,"CVSSData":20,"ExploitabilityScore":28,"ImpactScore":29},"nvd@nist.gov","Primary",{"Version":21,"VectorString":13,"AttackVector":22,"AttackComplexity":23,"PrivilegesRequired":24,"UserInteraction":25,"Scope":26,"ConfidentialityImpact":27,"IntegrityImpact":27,"AvailabilityImpact":27,"BaseScore":12,"BaseSeverity":27,"ExploitCodeMaturity":15,"RemediationLevel":15,"ReportConfidence":15,"TemporalScore":15,"TemporalSeverity":15,"ConfidentialityRequirement":15,"IntegrityRequirement":15,"AvailabilityRequirement":15,"ModifiedAttackVector":15,"ModifiedAttackComplexity":15,"ModifiedPrivilegesRequired":15,"ModifiedUserInteraction":15,"ModifiedScope":15,"ModifiedConfidentialityImpact":15,"ModifiedIntegrityImpact":15,"ModifiedAvailabilityImpact":15,"EnvironmentalScore":15,"EnvironmentalSeverity":15},"3.0","LOCAL","LOW","NONE","REQUIRED","UNCHANGED","HIGH",1.8,5.9,[31],{"Source":18,"Type":19,"CVSSData":32,"BaseSeverity":36,"ExploitabilityScore":39,"ImpactScore":40,"ACInsufInfo":15,"ObtainAllPrivilege":15,"ObtainUserPrivilege":15,"ObtainOtherPrivilege":15,"UserInteractionRequired":4},{"Version":33,"VectorString":34,"AccessVector":35,"AccessComplexity":36,"Authentication":24,"ConfidentialityImpact":37,"IntegrityImpact":37,"AvailabilityImpact":37,"BaseScore":38,"BaseSeverity":15,"Exploitability":15,"RemediationLevel":15,"ReportConfidence":15,"TemporalScore":15,"CollateralDamagePotential":15,"TargetDistribution":15,"ConfidentialityRequirement":15,"IntegrityRequirement":15,"AvailabilityRequirement":15,"EnvironmentalScore":15},"2.0","AV:N\u002FAC:M\u002FAu:N\u002FC:P\u002FI:P\u002FA:P","NETWORK","MEDIUM","PARTIAL",6.8,8.6,6.4,0.02676,[41,41,41,41,41,41,41],"High",[45],{"vendor":46,"product":47,"version":48,"criteria":49,"vulnerable":4},"enlightenment","terminology","*","cpe:2.3:a:enlightenment:terminology:*:*:*:*:*:*:*:*",1,[52,59,63],{"url":53,"source":54,"tags":55},"https:\u002F\u002Fphab.enlightenment.org\u002FT7504","Enlightenment",[56,57,58],"Mitigation","Exploit","Vendor Advisory",{"url":60,"source":54,"tags":61},"https:\u002F\u002Fphab.enlightenment.org\u002FrTRM1ac204da9148e7bccb1b5f34b523e2094dfc39e2",[56,62,58],"Patch",{"url":64,"source":54,"tags":65},"https:\u002F\u002Fwww.enlightenment.org\u002Fnews\u002F2018-12-16-terminology-1.3.1",[56,58],3,[68],{"id":69,"name":70,"description":71,"extendedDescription":72,"status":73,"abstraction":74,"structure":75},"CWE-74","Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')","The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.","Software or other automated logic has certain assumptions about what constitutes data and control respectively. It is the lack of verification of these assumptions for user-controlled input that leads to injection problems. Injection problems encompass a wide variety of issues -- all mitigated in very different ways and usually attempted in order to alter the control flow of the process. For this reason, the most effective way to discuss these weaknesses is to note the distinct features that classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common -- i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed.","Incomplete","Class","Simple",false,[],{"title":79,"metaDescription":80,"keywords":81,"canonicalUrl":82,"structuredData":83},"What is CVE-2018-20167? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2018-20167, a high severity cyber security vulnerability from 2018. Terminology before 1.3.1 allows Remote Code Execution becau...","CVE-2018-20167, CVE-2018-20167 vulnerability, CVE-2018-20167 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2018, CVSS score, exploit, patch, remediation, enlightenment security, terminology vulnerability","\u002Fwhat-is\u002Fcve-2018-20167",{"@context":84,"@type":85,"headline":79,"description":80,"datePublished":10,"dateModified":11,"author":86,"publisher":90,"about":94,"mainEntityOfPage":98,"articleSection":101,"keywords":102},"https:\u002F\u002Fschema.org","TechArticle",{"@type":87,"name":88,"url":89},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":87,"name":88,"url":89,"logo":91},{"@type":92,"url":93},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":95,"name":6,"description":96,"additionalType":97},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":99,"@id":100},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2018-20167","Cybersecurity","CVE-2018-20167, CVE-2018-20167 vulnerability, CVE-2018-20167 security, high severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[104],{"Operator":15,"Negate":15,"Nodes":105},[106],{"Operator":107,"Negate":15,"CPEMatch":108},"OR",[109],{"Vulnerable":4,"Criteria":49,"MatchCriteriaID":110,"VersionStartExcluding":15,"VersionStartIncluding":15,"VersionEndExcluding":111,"VersionEndIncluding":15},"50EE21A0-A88C-41C7-B21E-C626D2237B27","1.3.1",[],[],{"lastModified":11,"cacheTime":115,"version":33},1792267470203,{"score":117,"band":118,"action":119,"scoredAt":120},48,"Medium","Plan remediation","2026-10-16T06:45:14.913841+00:00"]