[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fhUoUnSqn7H-rS5TAppxO4tMrUZf2BNzICpJqYH_ydq4":3,"g5a-risk:CVE-2022-30744":121},{"success":4,"data":5,"meta":119},true,{"cveId":6,"title":7,"description":8,"shortDescription":8,"publishedDate":9,"lastModified":10,"cvssScore":11,"cvssVector":12,"cvssMetrics":13,"epssScore":47,"epssPercentile":26,"epssTimeSeries":48,"severity":50,"affectedProducts":51,"affectedProductsCount":57,"references":58,"referencesCount":57,"weaknesses":64,"weaknessesCount":80,"isActivelyExploited":81,"cisaInfo":26,"otxData":26,"relatedBlogPosts":82,"seoMetadata":83,"configurations":108,"relatedVendorCves":117,"notableEvents":118},"CVE-2022-30744","What is CVE-2022-30744?","DLL hijacking vulnerability in KiesWrapper in Samsung Kies prior to version 2.6.4.22043_1 allows attacker to execute arbitrary code.","2022-06-07T19:15:10.67","2022-06-13T18:57:15.287",7.8,"CVSS:3.1\u002FAV:L\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:U\u002FC:H\u002FI:H\u002FA:H",{"CVSSMetricV31":14,"CVSSMetricV30":26,"CVSSMetricV2":38,"CVSSMetricV40":26},[15,29],{"Source":16,"Type":17,"CVSSData":18,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":19,"VectorString":12,"AttackVector":20,"AttackComplexity":21,"PrivilegesRequired":22,"UserInteraction":23,"Scope":24,"ConfidentialityImpact":25,"IntegrityImpact":25,"AvailabilityImpact":25,"BaseScore":11,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":25,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"3.1","LOCAL","LOW","NONE","REQUIRED","UNCHANGED","HIGH",null,1.8,5.9,{"Source":30,"Type":31,"CVSSData":32,"ExploitabilityScore":36,"ImpactScore":37},"mobile.security@samsung.com","Secondary",{"Version":19,"VectorString":33,"AttackVector":20,"AttackComplexity":21,"PrivilegesRequired":22,"UserInteraction":22,"Scope":24,"ConfidentialityImpact":22,"IntegrityImpact":25,"AvailabilityImpact":22,"BaseScore":34,"BaseSeverity":35,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":22,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"CVSS:3.1\u002FAV:L\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:N\u002FI:H\u002FA:N",6.2,"MEDIUM",2.5,3.6,[39],{"Source":16,"Type":17,"CVSSData":40,"BaseSeverity":35,"ExploitabilityScore":45,"ImpactScore":46,"ACInsufInfo":26,"ObtainAllPrivilege":26,"ObtainUserPrivilege":26,"ObtainOtherPrivilege":26,"UserInteractionRequired":4},{"Version":41,"VectorString":42,"AccessVector":20,"AccessComplexity":35,"Authentication":22,"ConfidentialityImpact":43,"IntegrityImpact":43,"AvailabilityImpact":43,"BaseScore":44,"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:L\u002FAC:M\u002FAu:N\u002FC:P\u002FI:P\u002FA:P","PARTIAL",4.4,3.4,6.4,0.00249,[49,49,49,49,49,49,47],0.0024,"High",[52],{"vendor":53,"product":54,"version":55,"criteria":56,"vulnerable":4},"samsung","kies","*","cpe:2.3:a:samsung:kies:*:*:*:*:*:*:*:*",1,[59],{"url":60,"source":61,"tags":62},"https:\u002F\u002Fsecurity.samsungmobile.com\u002FserviceWeb.smsb?year=2022&month=6","Samsungmobile",[63],"Vendor Advisory",[65,73],{"id":66,"name":67,"description":68,"extendedDescription":69,"status":70,"abstraction":71,"structure":72},"CWE-427","Uncontrolled Search Path Element","The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.","Although this weakness can occur with any type of resource, it is frequently introduced when a product uses a directory search path to find executables or code libraries, but the path contains a directory that can be modified by an attacker, such as \"\u002Ftmp\" or the current working directory.\nIn Windows-based systems, when the LoadLibrary or LoadLibraryEx function is called with a DLL name that does not contain a fully qualified path, the function follows a search order that includes two path elements that might be uncontrolled:\nIn some cases, the attack can be conducted remotely, such as when SMB or WebDAV network shares are used.\nOne or more locations in that path could include the Windows drive root or its subdirectories. This often exists in Linux-based code assuming the controlled nature of the root directory (\u002F) or its subdirectories (\u002Fetc, etc), or a code that recursively accesses the parent directory.  In Windows, the drive root and some of its subdirectories have weak permissions by default, which makes them uncontrolled.\nIn some Unix-based systems, a PATH might be created that contains an empty element, e.g. by splicing an empty variable into the PATH. This empty element can be interpreted as equivalent to the current working directory, which might be an untrusted search element.\nIn software package management frameworks (e.g., npm, RubyGems, or PyPi), the framework may identify dependencies on third-party libraries or other packages, then consult a repository that contains the desired package. The framework may search a public repository before a private repository. This could be exploited by attackers by placing a malicious package in the public repository that has the same name as a package from the private repository. The search path might not be directly under control of the developer relying on the framework, but this search order effectively contains an untrusted element.","Draft","Base","Simple",{"id":74,"name":75,"description":76,"extendedDescription":77,"status":78,"abstraction":79,"structure":72},"CWE-20","Improper Input Validation","The product receives input or data, but it does\n        not validate or incorrectly validates that the input has the\n        properties that are required to process the data safely and\n        correctly.","Input validation is a frequently-used technique\n\t   for checking potentially dangerous inputs in order to\n\t   ensure that the inputs are safe for processing within the\n\t   code, or when communicating with other components.  When\n\t   software does not validate input properly, an attacker is\n\t   able to craft the input in a form that is not expected by\n\t   the rest of the application. This will lead to parts of the\n\t   system receiving unintended input, which may result in\n\t   altered control flow, arbitrary control of a resource, or\n\t   arbitrary code execution.\nInput validation is not the only technique for\n\t   processing input, however.  Other techniques attempt to\n\t   transform potentially-dangerous input into something safe, such\n\t   as filtering (CWE-790) - which attempts to remove dangerous\n\t   inputs - or encoding\u002Fescaping (CWE-116), which attempts to\n\t   ensure that the input is not misinterpreted when it is included\n\t   in output to another component. Other techniques exist as well\n\t   (see CWE-138 for more examples.)\nInput validation can be applied to:\nData can be simple or structured.  Structured data\n\t   can be composed of many nested layers, composed of\n\t   combinations of metadata and raw data, with other simple or\n\t   structured data.\nMany properties of raw data or metadata may need\n\t   to be validated upon entry into the code, such\n\t   as:\nImplied or derived properties of data must often\n\t   be calculated or inferred by the code itself.  Errors in\n\t   deriving properties may be considered a contributing factor\n\t   to improper input validation.\nNote that \"input validation\" has very different\n\t   meanings to different people, or within different\n\t   classification schemes.  Caution must be used when\n\t   referencing this CWE entry or mapping to it.  For example,\n\t   some weaknesses might involve inadvertently giving control\n\t   to an attacker over an input when they should not be able\n\t   to provide an input at all, but sometimes this is referred\n\t   to as input validation.\nFinally, it is important to emphasize that the\n\t   distinctions between input validation and output escaping\n\t   are often blurred, and developers must be careful to\n\t   understand the difference, including how input validation\n\t   is not always sufficient to prevent vulnerabilities,\n\t   especially when less stringent data types must be\n\t   supported, such as free-form text. Consider a SQL injection\n\t   scenario in which a person's last name is inserted into a\n\t   query. The name \"O'Reilly\" would likely pass the validation\n\t   step since it is a common last name in the English\n\t   language. However, this valid name cannot be directly\n\t   inserted into the database because it contains the \"'\"\n\t   apostrophe character, which would need to be escaped or\n\t   otherwise transformed. In this case, removing the\n\t   apostrophe might reduce the risk of SQL injection, but it\n\t   would produce incorrect behavior because the wrong name\n\t   would be recorded.","Stable","Class",2,false,[],{"title":84,"metaDescription":85,"keywords":86,"canonicalUrl":87,"structuredData":88},"What is CVE-2022-30744? Vulnerability Analysis | Security Advisory | EdgeProtect","Comprehensive analysis of CVE-2022-30744, a high severity cyber security vulnerability from 2022. DLL hijacking vulnerability in KiesWrapper in Samsung Kies ...","CVE-2022-30744, CVE-2022-30744 vulnerability, CVE-2022-30744 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, samsung security, kies vulnerability","\u002Fwhat-is\u002Fcve-2022-30744",{"@context":89,"@type":90,"headline":84,"description":85,"datePublished":9,"dateModified":10,"author":91,"publisher":95,"about":99,"mainEntityOfPage":103,"articleSection":106,"keywords":107},"https:\u002F\u002Fschema.org","TechArticle",{"@type":92,"name":93,"url":94},"Organization","EdgeProtect","https:\u002F\u002Fedgeprotect.io",{"@type":92,"name":93,"url":94,"logo":96},{"@type":97,"url":98},"ImageObject","https:\u002F\u002Fedgeprotect.io\u002Fimg\u002Flogos\u002Fedgeprotect-logo-512.png",{"@type":100,"name":6,"description":101,"additionalType":102},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":104,"@id":105},"WebPage","https:\u002F\u002Fedgeprotect.io\u002Fwhat-is\u002Fcve-2022-30744","Cybersecurity","CVE-2022-30744, CVE-2022-30744 vulnerability, CVE-2022-30744 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":56,"MatchCriteriaID":115,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":116,"VersionEndIncluding":26},"0B10192A-53B0-4BCB-8D44-9232B2A77C09","2.6.4.22043_1",[],[],{"lastModified":10,"cacheTime":120,"version":41},1793222083597,{"score":122,"band":123,"action":124,"scoredAt":125},46,"Medium","Plan remediation","2026-10-28T06:54:12.559101+00:00"]